2 |
Approval of the agenda |
|
R4-2203500 |
RAN4#101-bis-e Meeting Report |
ETSI MCC |
R4-2203501 |
Agenda for RAN4#102-e |
RAN4 Chair (Huawei) |
R4-2203502 |
RAN4#102-e E-Meeting Arrangements and Guidelines |
RAN4 Chair (Huawei) |
R4-2206144 |
RAN4#101-bis-e Meeting Report |
ETSI MCC |
R4-2206646 |
RRM Session meeting minutes |
Vice Chair (Intel) |
R4-2206647 |
BS_Demod_Testing Session meeting minutes |
Vice Chair (Samsung) |
3 |
Letters / reports from other groups / meeting |
|
R4-2203503 |
LS on updated Rel-17 NR higher-layers parameter list |
RAN1 |
R4-2203504 |
LS on DMRS bundling for PUSCH and PUCCH |
RAN1 |
R4-2203505 |
LS on updated Rel-17 RAN1 UE features list for NR |
RAN1 |
R4-2203506 |
LS on a minimum guard period between two SRS resources for antenna switching |
RAN1 |
R4-2203507 |
LS on efficient activation/de-activation mechanism for one SCG |
RAN2 |
R4-2203508 |
LS to RAN4 on RAN2 agreement for MUSIM gaps |
RAN2 |
R4-2203509 |
Reply LS on the use of NCD-SSB or CSI-RS in DL BWPs for RedCap UEs |
RAN2 |
R4-2203510 |
LS on RSRP measurement before Msg1 or MsgA retransmission |
RAN2 |
R4-2203511 |
Response LS on the reporting of the Tx TEG association information |
RAN2 |
R4-2203512 |
Reply LS on Multiple SMTCs for NR NTN |
RAN2 |
R4-2203513 |
Reply LS on NR NTN Neighbor Cell and Satellite Information |
RAN2 |
R4-2203514 |
Reply LS on HO with PSCell from NR SA to EN-DC |
RAN2 |
R4-2203515 |
Reply LS to RAN4 on NCSG |
RAN2 |
R4-2203516 |
LS on PDC for Time Synchronization |
RAN2 |
R4-2203517 |
Reply LS on DC location for >2CC |
RAN2 |
R4-2203518 |
LS to RAN4 on RLM/BFD relaxation for ePowSav |
RAN2 |
R4-2203519 |
LS on feMIMO RRC parameters |
RAN2 |
R4-2203520 |
Reply LS on latency improvement for PRS measurement with MG |
RAN2 |
R4-2203521 |
Reply LS on energy efficiency as guiding principle for new solutions |
SA5 |
R4-2206145 |
Reply LS on Rel-17 RAN1 and RAN4 feature list |
RAN2 |
R4-2206146 |
LS on updated Rel-17 LTE and NR higher-layers parameter list |
RAN1 |
R4-2206147 |
Reply LS on interruption for PUCCH SCell activation in invalid TA case |
RAN1 |
R4-2206148 |
Reply LS on the applicability of PRS processing window in RRC_INACTIVE state |
RAN1 |
R4-2206149 |
Reply LS on SRS for multi-RTT positioning |
RAN1 |
R4-2206150 |
Reply LS on UE capability for supporting single DCI transmission schemes for multi-TRP |
RAN1 |
R4-2206151 |
LS on feMIMO RRC parameters |
RAN1 |
R4-2206152 |
Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure |
RAN1 |
R4-2206153 |
Reply LS on CORESET#0 impact of CBW narrower than 40MHz of n79 |
RAN1 |
R4-2206154 |
LS response on MPE information signaling |
RAN1 |
R4-2206155 |
LS on upper layers parameters for Rel-17 eIAB |
RAN1 |
R4-2206156 |
Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
RAN1 |
R4-2206157 |
Reply LS to RAN4 on PEMAX for NR-V2X |
RAN1 |
R4-2206158 |
Reply LS on Pemax for NR-V2X |
RAN2 |
R4-2206159 |
Reply LS on range of power control parameters for eIAB |
RAN1 |
4.1.1 |
UE RF requirements |
|
R4-2204069 |
Discussion on the common UE RF requirement tables for the release independent features in TS 36.307 and TS 38.307 |
CHTTL, ZTE |
R4-2204070 |
draft CR for the procedure of introducing release independent features |
CHTTL, ZTE |
R4-2204071 |
draft CR for the procedure of introducing release independent features |
CHTTL, ZTE |
R4-2204072 |
draft CR for the procedure of introducing release independent features |
CHTTL, ZTE |
R4-2206285 |
draft CR to 38.101-1 on AMPR edge RB allocation for NS R15 |
Apple |
R4-2206287 |
draft CR for the procedure of introducing release independent features |
CHTTL, ZTE |
R4-2206295 |
WF on FR1 UL coherent MIMO |
Main Session |
R4-2206296 |
Further Reply LS on requirement in Power Class 2 for UL MIMO |
Vivo |
R4-2206299 |
WF on Transient period capability |
Main Session |
R4-2206301 |
Email discussion summary for [102-e][101] R15_Maintenance |
Moderator (ZTE) |
R4-2206401 |
Email discussion summary for [102-e][101] R15_Maintenance |
Moderator (ZTE) |
R4-2206619 |
Big CR for TS 38.307 Maintenance (Rel-15) |
MCC |
R4-2206620 |
Big CR for TS 38.307 Maintenance (Rel-16) |
MCC |
R4-2206621 |
Big CR for TS 38.307 Maintenance (Rel-17) |
MCC |
R4-2206622 |
Big CR for TS 36.101 Maintenance (Rel-14) |
MCC, Xiaomi |
R4-2206623 |
Big CR for TS 36.101 Maintenance (Rel-15) |
MCC, Xiaomi |
R4-2206624 |
Big CR for TS 36.101 Maintenance (Rel-16) |
MCC, Xiaomi |
R4-2206625 |
Big CR for TS 36.101 Maintenance (Rel-17) |
MCC, Xiaomi |
4.1.1.1 |
FR1 (38.101-1) |
|
R4-2203605 |
Correction to FR1 UL RMCs |
Rohde & Schwarz |
R4-2203606 |
Correction to FR1 UL RMCs |
Rohde & Schwarz |
R4-2203607 |
Correction to FR1 UL RMCs |
Rohde & Schwarz |
R4-2203670 |
draftCR for TS 38.101-1 Rel-15: Corrections on single bands for UE co-existence |
Apple |
R4-2203671 |
draftCR for TS 38.101-1 Rel-16: Corrections on single bands for UE co-existence |
Apple |
R4-2203672 |
draftCR for TS 38.101-1 Rel-17: Corrections on single bands for UE co-existence |
Apple |
R4-2203678 |
draft CR to 38.101-1 on AMPR edge RB allocation for NS R15 |
Apple |
R4-2203679 |
draft CR to 38.101-1 on AMPR edge RB allocation for NS R16 |
Apple |
R4-2203680 |
draft CR to 38.101-1 on AMPR edge RB allocation for NS R17 |
Apple |
R4-2203999 |
Draft CR to TS 38.101-1 on removal the bracket for the note of NS_01 |
ZTE Corporation |
R4-2204000 |
Draft CR to TS 38.101-1 on removal the bracket for the note of NS_01 (R16_CAT_A) |
ZTE Corporation |
R4-2204001 |
Draft CR to TS 38.101-1 on removal the bracket for the note of NS_01 (R17_CAT_A) |
ZTE Corporation |
R4-2204165 |
CR CatA n74 AMPR |
Qualcomm Incorporated |
R4-2204167 |
CR CatA n74 AMPR |
Qualcomm Incorporated |
R4-2204175 |
n1 NS_05 ineqaulity error fix Cat F rel 15 |
Qualcomm Incorporated |
R4-2204176 |
n1 NS_05 ineqaulity error fix Cat A rel 16 |
Qualcomm Incorporated |
R4-2204177 |
n1 NS_05 ineqaulity error fix Cat A rel 17 |
Qualcomm Incorporated |
R4-2204596 |
Correction to Pcmax: application of p-NR-FR1 for one CG with one uplink serving cell |
Ericsson |
R4-2204597 |
Correction to Pcmax: application of p-NR-FR1 for one CG with one uplink serving cell |
Ericsson |
R4-2204598 |
Correction to Pcmax: application of p-NR-FR1 for one CG with one uplink serving cell |
Ericsson |
R4-2204599 |
Correction to relative power tolerance |
Ericsson |
R4-2204600 |
Correction to relative power tolerance |
Ericsson |
R4-2204601 |
Correction to relative power tolerance |
Ericsson |
R4-2204967 |
On draft reply LS in Power class issues for Rel-15 |
vivo |
R4-2205220 |
DraftCR for TS 38.101-1 on correction on IL for SRS antenna switching |
ZTE Wistron Telecom AB |
R4-2205221 |
DraftCR for TS 38.101-1 on correction on IL for SRS antenna switching |
ZTE Wistron Telecom AB |
R4-2205222 |
DraftCR for TS 38.101-1 on correction on IL for SRS antenna switching |
ZTE Wistron Telecom AB |
R4-2205294 |
Draft CR for 38.101-1 to align the UL channel bandwidth between clause 6.5.3.3 and 6.2.3.1 for n74(R15) |
Huawei, HiSilicon |
R4-2205295 |
Draft CR for 38.101-1 to align the UL channel bandwidth between clause 6.5.3.3 and 6.2.3.1 for n74(R16) |
Huawei, HiSilicon |
R4-2205296 |
Draft CR for 38.101-1 to align the UL channel bandwidth between clause 6.5.3.3 and 6.2.3.1 for n74(R17) |
Huawei, HiSilicon |
R4-2205301 |
Draft CR for 38.101-1 to add spurious response exception for intra-band CA(R15) |
Huawei, HiSilicon |
R4-2205302 |
Draft CR for 38.101-1 to add spurious response exception for intra-band CA(R16) |
Huawei, HiSilicon |
R4-2205303 |
Draft CR for 38.101-1 to add spurious response exception for intra-band CA(R17) |
Huawei, HiSilicon |
R4-2205610 |
FR1 UL coherent MIMO |
Anritsu Limited |
R4-2205617 |
General SE requirements for n41 |
Anritsu Limited |
R4-2205618 |
Draft CR to correct the general SE requirements for n41 |
Anritsu Limited |
R4-2205619 |
Draft CR to correct the general SE requirements for n41 |
Anritsu Limited |
R4-2205620 |
Draft CR to correct the general SE requirements for n41 |
Anritsu Limited |
R4-2206099 |
MIMO EVM Measurement for FR1 |
Lenovo |
R4-2206286 |
Draft CR to TS 38.101-1 on removal the bracket for the note of NS_01 |
ZTE Corporation |
R4-2206288 |
n1 NS_05 ineqaulity error fix Cat F rel 15 |
Qualcomm Incorporated |
R4-2206289 |
DraftCR for TS 38.101-1 on correction on IL for SRS antenna switching |
ZTE Wistron Telecom AB |
R4-2206290 |
Draft CR for 38.101-1 to align the UL channel bandwidth between clause 6.5.3.3 and 6.2.3.1 for n74(R15) |
Huawei, HiSilicon |
R4-2206610 |
Big CR for TS 38.101-1 Maintenance Part-1 (Rel-15) |
MCC, OPPO |
R4-2206611 |
Big CR for TS 38.101-1 Maintenance Part-1 (Rel-16) |
MCC, OPPO |
R4-2206612 |
Big CR for TS 38.101-1 Maintenance Part-1 (Rel-17) |
MCC, OPPO |
R4-2206613 |
Big CR for TS 38.101-2 Maintenance (Rel-15) |
MCC, Samsung |
R4-2206614 |
Big CR for TS 38.101-2 Maintenance (Rel-16) |
MCC, Samsung |
R4-2206615 |
Big CR for TS 38.101-2 Maintenance (Rel-17) |
MCC, Samsung |
4.1.1.2 |
FR2 (38.101-2) |
|
R4-2203608 |
Correction to Rel-15 FR2 RMCs |
Rohde & Schwarz |
R4-2203609 |
Correction to Rel-15 FR2 RMCs |
Rohde & Schwarz |
R4-2203610 |
Correction to Rel-15 FR2 RMCs |
Rohde & Schwarz |
R4-2203811 |
Correction of FR2 UE configured transmitted power |
Apple |
R4-2204002 |
Draft CR to TS 38.101-2 on corrections to UE maximum output power with additional requirements |
ZTE Corporation |
R4-2204003 |
Draft CR to TS 38.101-2 on corrections to UE maximum output power with additional requirements (R16_CAT_A) |
ZTE Corporation |
R4-2204004 |
Draft CR to TS 38.101-2 on corrections to UE maximum output power with additional requirements (R17_CAT_A) |
ZTE Corporation |
R4-2206063 |
Draft CR to 38.101-2: missing image location for CA IBE (cat. F) |
Qualcomm Incorporated |
R4-2206064 |
Draft CR to 38.101-2: missing image location for CA IBE (cat. A) |
Qualcomm Incorporated |
R4-2206065 |
Draft CR to 38.101-2: missing image location for CA IBE (cat. A) |
Qualcomm Incorporated |
4.1.1.3 |
Requirements for 38.101-3 |
|
R4-2203991 |
Draft CR to TS 38.307 on NR intra-band CA BW class within FR1 (Rel-15) |
ZTE Corporation |
R4-2205304 |
Draft CR for 38.101-3 to add spurious response exception for intra-band EN-DC (R15) |
Huawei, HiSilicon |
R4-2205305 |
Draft CR for 38.101-3 to add spurious response exception for intra-band EN-DC (R16) |
Huawei, HiSilicon |
R4-2205306 |
Draft CR for 38.101-3 to add spurious response exception for intra-band EN-DC (R17) |
Huawei, HiSilicon |
R4-2205614 |
Draft CR to correct the output power in EN-DC Rx tests |
Anritsu Limited |
R4-2205615 |
Draft CR to correct the output power in EN-DC Rx tests |
Anritsu Limited |
R4-2205616 |
Draft CR to correct the output power in EN-DC Rx tests |
Anritsu Limited |
R4-2205705 |
draft Rel-15 CR 38101-3-fg0 to align spurious emission between R15 and R16 |
Ericsson |
R4-2206291 |
Draft CR to correct the output power in EN-DC Rx tests |
Anritsu Limited |
R4-2206293 |
draft Rel-15 CR 38101-3-fg0 to align spurious emission between R15 and R16 |
Ericsson |
R4-2206589 |
Draft CR to TS 38.307 on NR intra-band CA BW class within FR1 (Rel-15) |
ZTE Corporation |
R4-2206616 |
Big CR for TS 38.101-3 Maintenance (Rel-15) |
MCC, Huawei |
R4-2206617 |
Big CR for TS 38.101-3 Maintenance (Rel-16) |
MCC, Huawei |
R4-2206618 |
Big CR for TS 38.101-3 Maintenance (Rel-17) |
MCC, Huawei |
4.1.2 |
UE EMC requirements |
|
R4-2207146 |
Email discussion summary for [102-e][303] NR_EMC |
Moderator (ZTE) |
R4-2207419 |
Email discussion summary for [102-e][303] NR_EMC |
Moderator (ZTE) |
4.1.3 |
BS RF requirements |
|
R4-2207144 |
Email discussion summary for [102-e][301] BSRF_Maintenance |
Moderator (Ericsson) |
R4-2207417 |
Email discussion summary for [102-e][301] BSRF_Maintenance |
Moderator (Ericsson) |
4.1.3.1 |
General |
|
R4-2203580 |
CR to TR 38.803: Addition of array antenna model extension in subclause 5.2.3 |
Ericsson |
R4-2207314 |
CR to TR 38.803: Addition of array antenna model extension in subclause 5.2.3 |
Ericsson |
4.1.3.3 |
MSR specifications |
|
R4-2204443 |
Draft CR to 37.104: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2204444 |
Draft CR to 37.104: BS OBUE requirements clarification, rel-16 |
NEC |
R4-2204445 |
Draft CR to 37.104: BS OBUE requirements clarification, rel-17 |
NEC |
R4-2204446 |
Draft CR to 37.105: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2204447 |
Draft CR to 37.105: BS OBUE requirements clarification, rel-16 |
NEC |
R4-2204448 |
Draft CR to 37.105: BS OBUE requirements clarification, rel-17 |
NEC |
R4-2204449 |
Draft CR to 37.141: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2204450 |
Draft CR to 37.141: BS OBUE requirements clarification, rel-16 |
NEC |
R4-2204451 |
Draft CR to 37.141: BS OBUE requirements clarification, rel-17 |
NEC |
R4-2204452 |
Draft CR to 37.145-1: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2204453 |
Draft CR to 37.145-1: BS OBUE requirements clarification, rel-16 |
NEC |
R4-2204454 |
Draft CR to 37.145-1: BS OBUE requirements clarification, rel-17 |
NEC |
R4-2204455 |
Draft CR to 37.145-2: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2204456 |
Draft CR to 37.145-2: BS OBUE requirements clarification, rel-16 |
NEC |
R4-2204457 |
Draft CR to 37.145-2: BS OBUE requirements clarification, rel-17 |
NEC |
R4-2207471 |
Big CR for TS 37.104 Maintenance (Rel-15, CAT F) |
MCC, Ericsson |
R4-2207472 |
Big CR for TS 37.104 Maintenance (Rel-16, CAT A) |
MCC, Ericsson |
R4-2207473 |
Big CR for TS 37.104 Maintenance (Rel-17, CAT A) |
MCC, Ericsson |
R4-2207474 |
Big CR for TS 37.105 Maintenance (Rel-15, CAT F) |
MCC, Huawei |
R4-2207475 |
Big CR for TS 37.105 Maintenance (Rel-16, CAT F) |
MCC, Huawei |
R4-2207476 |
Big CR for TS 37.105 Maintenance (Rel-17, CAT A) |
MCC, Huawei |
R4-2207477 |
Big CR for TS 37.141 Maintenance (Rel-15, CAT F) |
MCC, Ericsson |
R4-2207478 |
Big CR for TS 37.141 Maintenance (Rel-16, CAT F) |
MCC, Ericsson |
R4-2207479 |
Big CR for TS 37.141 Maintenance (Rel-17, CAT F) |
MCC, Ericsson |
R4-2207480 |
Big CR for TS 37.145-1 Maintenance (Rel-15, CAT F) |
MCC, Huawei |
R4-2207481 |
Big CR for TS 37.145-1 Maintenance (Rel-16, CAT F) |
MCC, Huawei |
R4-2207482 |
Big CR for TS 37.145-1 Maintenance (Rel-17, CAT A) |
MCC, Huawei |
R4-2207483 |
Big CR for TS 37.145-2 Maintenance (Rel-15, CAT F) |
MCC, Huawei |
R4-2207484 |
Big CR for TS 37.145-2 Maintenance (Rel-16, CAT F) |
MCC, Huawei |
R4-2207485 |
Big CR for TS 37.145-2 Maintenance (Rel-17, CAT A) |
MCC, Huawei |
R4-2207486 |
Big CR for TS 38.101-4 Maintenance (Rel-15, CAT F) |
MCC, Intel |
R4-2207487 |
Big CR for TS 38.101-4 Maintenance (Rel-16, CAT F) |
MCC, Intel |
R4-2207488 |
Big CR for TS 38.101-4 Maintenance (Rel-17, CAT F) |
MCC, Intel |
R4-2207489 |
Big CR for TS 38.104 Maintenance RF part (Rel-16, CAT F) |
MCC, Ericsson |
R4-2207490 |
Big CR for TS 38.104 Maintenance RF part (Rel-17, CAT F) |
MCC, Ericsson |
R4-2207491 |
Big CR for TS 38.141-1 Maintenance RF part (Rel-15, CAT F) |
MCC, CATT |
R4-2207492 |
Big CR for TS 38.141-1 Maintenance RF part (Rel-16, CAT F) |
MCC, CATT |
R4-2207493 |
Big CR for TS 38.141-1 Maintenance RF part (Rel-17, CAT A) |
MCC, CATT |
R4-2207494 |
Big CR for TS 38.141-2 Maintenance RF part (Rel-15, CAT F) |
MCC, Huawei |
R4-2207495 |
Big CR for TS 38.141-2 Maintenance RF part (Rel-16, CAT F) |
MCC, Huawei |
R4-2207496 |
Big CR for TS 38.141-2 Maintenance RF part (Rel-17, CAT A) |
MCC, Huawei |
R4-2207501 |
Big CR for TS 38.104 Maintenance Demod part (Rel-16, CAT F) |
MCC, Nokia |
R4-2207502 |
Big CR for TS 38.104 Maintenance Demod part (Rel-17, CAT A) |
MCC, Nokia |
R4-2207503 |
Big CR for TS 38.141-1 Maintenance Demod part(Rel-15, CAT F) |
MCC, Huawei |
R4-2207504 |
Big CR for TS 38.141-1 Maintenance Demod part (Rel-16, CAT A) |
MCC, Huawei |
R4-2207506 |
Big CR for TS 38.141-1 Maintenance Demod part (Rel-17, CAT A) |
MCC, Huawei |
R4-2207507 |
Big CR for TS 38.141-2 Maintenance Demod part(Rel-15, CAT F) |
MCC, Intel |
R4-2207508 |
Big CR for TS 38.141-2 Maintenance Demod part (Rel-16, CAT F) |
MCC, Intel |
R4-2207509 |
Big CR for TS 38.141-2 Maintenance Demod part (Rel-17, CAT A) |
MCC, Intel |
R4-2207530 |
Big CR for TS 38.141-1 Maintenance RF part (Rel-15, CAT F) |
MCC, CATT |
R4-2207531 |
Big CR for TS 38.141-1 Maintenance RF part (Rel-16, CAT F) |
MCC, CATT |
R4-2207532 |
Big CR for TS 38.141-1 Maintenance RF part (Rel-17, CAT A) |
MCC, CATT |
4.1.4.1 |
General |
|
R4-2203562 |
Sweep time setting of spectrum analyzer for BS unwanted emission TCs |
Anritsu Corporation |
R4-2203977 |
Discussion on sweep time for unwanted emission testing |
CATT |
R4-2204435 |
Discussion on the sweep time for unwanted emission testing |
NEC |
R4-2204711 |
setting Sweep Time Requirement on Measuring BS Conformance Unwanted Emission testing |
Keysight Technologies UK Ltd |
R4-2205149 |
Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2207145 |
Email discussion summary for [102-e][302] NR_Conformance_Maintenance |
Moderator (Huawei) |
R4-2207418 |
Email discussion summary for [102-e][302] NR_Conformance_Maintenance |
Moderator (Huawei) |
4.1.4.2 |
Conducted conformance testing (38.141-1) |
|
R4-2203978 |
draft CR for TS 38.141-1 On sweep time for unwanted emission testing (Rel-15) |
CATT |
R4-2203979 |
draft CR for TS 38.141-1 On sweep time for unwanted emission testing (Rel-16) |
CATT |
R4-2203980 |
draft CR for TS 38.141-1 On sweep time for unwanted emission testing (Rel-17) |
CATT |
R4-2205150 |
Draft CR to 38.141-1: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2205151 |
Draft CR to 38.141-1: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2205152 |
Draft CR to 38.141-1: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2207295 |
Draft CR to 38.141-1: Clarification for unwanted emission testing |
Huawei, HiSilicon |
4.1.4.3 |
Radiated conformance testing (38.141-2) |
|
R4-2203981 |
draft CR for TS 38.141-2 On sweep time for unwanted emission testing (Rel-15) |
CATT |
R4-2203982 |
draft CR for TS 38.141-2 On sweep time for unwanted emission testing (Rel-16) |
CATT |
R4-2203983 |
draft CR for TS 38.141-2 On sweep time for unwanted emission testing (Rel-17) |
CATT |
R4-2205153 |
Draft CR to 38.141-2: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2205154 |
Draft CR to 38.141-2: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2205155 |
Draft CR to 38.141-2: Clarification for unwanted emission testing |
Huawei, HiSilicon |
R4-2207296 |
draft CR for TS 38.141-2 On sweep time for unwanted emission testing (Rel-15) |
CATT |
4.1.4.4 |
eAAS specifications |
|
R4-2205159 |
Correction on the test configuration for NC operation 37.141 R16 |
Huawei, HiSilicon |
R4-2205160 |
Correction on the test configuration for NC operation 37.141 R17 |
Huawei, HiSilicon |
R4-2205161 |
Correction on the test configuration for NC operation 37.145-1 R16 |
Huawei, HiSilicon |
R4-2205162 |
Correction on the test configuration for NC operation 37.145-1 R17 |
Huawei, HiSilicon |
R4-2205163 |
Correction on the test configuration for NC operation 37.145-2 R16 |
Huawei, HiSilicon |
R4-2205164 |
Correction on the test configuration for NC operation 37.145-2 R17 |
Huawei, HiSilicon |
R4-2207297 |
Correction on the test configuration for NC operation 37.141 R16 |
Huawei, HiSilicon |
R4-2207298 |
Correction on the test configuration for NC operation 37.145-2 R16 |
Huawei, HiSilicon |
R4-2207299 |
Correction on the test configuration for NC operation 37.145-1 R16 |
Huawei, HiSilicon |
4.1.5 |
BS EMC requirements |
|
R4-2204429 |
Further discussion on highest frequency and measurement uncertainty for NR BS radiated emission test |
ZTE |
R4-2204458 |
Draft CR to TS 38.113: Radiated emission measurement uncertainty (R15) |
ZTE |
R4-2204459 |
Draft CR to TS 38.113: Radiated emission measurement uncertainty (R16) |
ZTE |
R4-2205853 |
TS 25.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2205854 |
TS 25.113: Correction in clause 9 Immunity |
Ericsson |
R4-2205855 |
TS 36.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2205856 |
TS 36.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2205857 |
TS 37.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2205858 |
TS 37.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2205859 |
TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2205860 |
TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2205861 |
TS 38.113: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2205862 |
TS 38.113: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207187 |
WF on NR repeater EMC testing |
Nokia |
R4-2207188 |
WF on MU value for the radiated emission measurements |
ZTE Corporation |
4.1.6 |
RRM core requirements (38.133/36.133) |
|
R4-2203593 |
Maintenance for cell phase synchronization accuracy |
ZTE Corporation |
R4-2203594 |
Maintenance for cell phase synchronization accuracy R16 Cat A |
ZTE Corporation |
R4-2203595 |
Maintenance for cell phase synchronization accuracy R17 Cat A |
ZTE Corporation |
R4-2203799 |
Draft CR on core part maintenance for TS36.133 R15 |
Apple |
R4-2203800 |
Draft CR on core part maintenance for TS36.133 R16 |
Apple |
R4-2203801 |
Draft CR on core part maintenance for TS36.133 R17 |
Apple |
R4-2203837 |
draft Cat-F CR (R15) to SCell Activation Core |
Qualcomm Incorporated |
R4-2203838 |
draft Cat-A CR (R16) to SCell Activation Core |
Qualcomm Incorporated |
R4-2203839 |
draft Cat-A CR (R17) to SCell Activation Core |
Qualcomm Incorporated |
R4-2204178 |
Discussion on applicable DRX cycle in NE-DC and NR-DC mode inter-frequency measurement |
MediaTek inc. |
R4-2204179 |
CR on TS38.133 for applicable DRX cycle in NR-DC and NE-DC inter-frequency measurement |
MediaTek inc. |
R4-2204180 |
CR on TS38.133 for applicable DRX cycle in NR-DC and NE-DC inter-frequency measurement |
MediaTek inc. |
R4-2204181 |
CR on TS38.133 for applicable DRX cycle in NR-DC and NE-DC inter-frequency measurement |
MediaTek inc. |
R4-2204308 |
Draft CR to maintain inter-RAT measurements in TS 36.133 |
OPPO |
R4-2204309 |
Draft CR to maintain inter-RAT measurements in TS 36.133 |
OPPO |
R4-2204310 |
Draft CR to maintain inter-RAT measurements in TS 36.133 |
OPPO |
R4-2204544 |
On DRX configurations for NR-DC and NE-DC |
Nokia, Nokia Shanghai Bell |
R4-2204552 |
Draft CR to maintain inter-RAT measurements subject to CCA in TS 36.133 |
OPPO |
R4-2204553 |
Draft CR to maintain inter-RAT measurements subject to CCA in TS 36.133 |
OPPO |
R4-2204802 |
Draft CR on R15 inter-RAT LTE measurement |
vivo Ericsson |
R4-2204803 |
Draft CR on R16 inter-RAT LTE measurement |
vivo Ericsson |
R4-2204804 |
Draft CR on R17 inter-RAT LTE measurement |
vivo |
R4-2204838 |
Correction to SCell Interruptions requirements_EUTRA_R15 |
Huawei, Hisilicon |
R4-2204839 |
Correction to SCell Interruptions requirements_EUTRA_R16 |
Huawei, Hisilicon |
R4-2204840 |
Correction to SCell Interruptions requirements_EUTRA_R17 |
Huawei, Hisilicon |
R4-2204841 |
Correction to SCell Interruptions requirements_NR_R15 |
Huawei, Hisilicon |
R4-2204842 |
Correction to SCell Interruptions requirements_NR_R16 |
Huawei, Hisilicon |
R4-2204843 |
Correction to SCell Interruptions requirements_NR_R17 |
Huawei, Hisilicon |
R4-2205341 |
CR on SCell activation delay requirements 38133 R15 |
Huawei, HiSilicon, Apple |
R4-2205342 |
CR on SCell activation delay requirements 38133 R16 |
Huawei, HiSilicon, Apple |
R4-2205343 |
CR on SCell activation delay requirements 38133 R17 |
Huawei, HiSilicon, Apple |
R4-2205344 |
CR on RSTD measurement requirements 36133 R15 |
Huawei, HiSilicon |
R4-2205345 |
CR on RSTD measurement requirements 36133 R16 |
Huawei, HiSilicon |
R4-2205346 |
CR on RSTD measurement requirements 36133 R17 |
Huawei, HiSilicon |
R4-2205406 |
[draft CR] R15 Maintenance for 38133 |
ZTE Corporation |
R4-2205407 |
[draft CR] R15 Maintenance for 38133 (R16 Cat A) |
ZTE Corporation |
R4-2205408 |
[draft CR] R15 Maintenance for 38133 (R17 Cat A) |
ZTE Corporation |
R4-2205518 |
Remaining issue for Idle mode |
Ericsson |
R4-2205519 |
draftCR on RRM remaining issues - r15 |
Ericsson |
R4-2205520 |
draftCR on RRM remaining issues - r16 |
Ericsson |
R4-2205521 |
draftCR on RRM remaining issues - r17 |
Ericsson |
R4-2206022 |
Correction to reference point defintion for UE timing in TS 38.133 |
Ericsson, Intel, Huawei, HiSilicon, Qualcomm |
R4-2206023 |
Correction to reference point defintion for UE timing in TS 38.133 |
Ericsson, Intel, Huawei, HiSilicon, Qualcomm |
R4-2206024 |
Correction to reference point defintion for UE timing in TS 38.133 |
Ericsson, Intel, Huawei, HiSilicon, Qualcomm |
R4-2206744 |
Email discussion summary for [102-e][201] Maintenance_R15_NR_RRM |
Moderator (Huawei) |
R4-2206791 |
WF on remaining issues in Rel-15 NR RRM |
Huawei, HiSilicon |
R4-2206792 |
Draft CR on core part maintenance for TS36.133 R15 |
Apple |
R4-2206793 |
draft Cat-F CR (R15) to SCell Activation Core |
Qualcomm Incorporated |
R4-2206794 |
CR on TS38.133 for applicable DRX cycle in NR-DC and NE-DC inter-frequency measurement |
MediaTek inc. |
R4-2206795 |
Draft CR to maintain inter-RAT measurements in TS 36.133 |
OPPO |
R4-2206796 |
Draft CR on R15 inter-RAT LTE measurement |
vivo Ericsson |
R4-2206797 |
Correction to SCell Interruptions requirements_EUTRA_R15 |
Huawei, Hisilicon |
R4-2206798 |
Correction to SCell Interruptions requirements_NR_R15 |
Huawei, Hisilicon |
R4-2206799 |
CR on SCell activation delay requirements 38133 R15 |
Huawei, HiSilicon, Apple |
R4-2206800 |
CR on SCell activation delay requirements 38133 R16 |
Huawei, HiSilicon, Apple |
R4-2206801 |
CR on RSTD measurement requirements 36133 R15 |
Huawei, HiSilicon |
R4-2206802 |
draftCR on RRM remaining issues - r15 |
Ericsson |
R4-2207042 |
Email discussion summary for [102-e][201] Maintenance_R15_NR_RRM |
Moderator (Huawei) |
R4-2207133 |
Big CR to TS 38.133: NR_newRAT-Core maintenance (Rel-15) |
MCC, Apple |
R4-2207134 |
Big CR to TS 38.133: NR_newRAT-Core maintenance (Rel-16) |
MCC, Apple |
R4-2207135 |
Big CR to TS 38.133: NR_newRAT-Core maintenance (Rel-17) |
MCC, Apple |
4.1.7 |
RRM performance requirements (38.133/36.133) |
|
R4-2203563 |
Reduction of allocated RBs for CSI-RS based RLM TC in FR2 |
Anritsu Corporation |
R4-2203564 |
Reduction of allocated RBs for CSI-RS based RLM TC in FR2 |
Anritsu Corporation |
R4-2203565 |
Reduction of allocated RBs for CSI-RS based RLM TC in FR2 |
Anritsu Corporation |
R4-2203566 |
FR2 Inter-frequency Relative SS-RSRP accuracy |
Anritsu Corporation |
R4-2203567 |
Correction on the FR2 inter-frequency relative RSRP accuracy |
Anritsu Corporation, MediaTek Inc. |
R4-2203568 |
Correction on the FR2 inter-frequency relative RSRP accuracy |
Anritsu Corporation, MediaTek Inc. |
R4-2203569 |
Correction on the FR2 inter-frequency relative RSRP accuracy |
Anritsu Corporation, MediaTek Inc. |
R4-2203570 |
Draft CR to maintain performance requirement |
Anritsu Corporation |
R4-2203571 |
Draft CR to maintain performance requirement |
Anritsu Corporation |
R4-2203572 |
Draft CR to maintain performance requirement |
Anritsu Corporation |
R4-2203596 |
Draft CR to TS 38.133: Corrections to active TCI state switch test cases (Rel 15) |
Rohde & Schwarz |
R4-2203597 |
Draft CR to TS 38.133: Corrections to active TCI state switch test cases (Rel 16) |
Rohde & Schwarz |
R4-2203598 |
Draft CR to TS 38.133: Corrections to active TCI state switch test cases (Rel 17) |
Rohde & Schwarz |
R4-2203599 |
Draft CR to TS 38.133: Corrections to inter-RAT measurement test cases (Rel 15) |
Rohde & Schwarz |
R4-2203600 |
Draft CR to TS 38.133: Corrections to inter-RAT measurement test cases (Rel 16) |
Rohde & Schwarz |
R4-2203601 |
Draft CR to TS 38.133: Corrections to inter-RAT measurement test cases (Rel 17) |
Rohde & Schwarz |
R4-2203602 |
Draft CR to TS 38.133: Corrections to intra-frequency event triggered test cases (Rel 15) |
Rohde & Schwarz |
R4-2203603 |
Draft CR to TS 38.133: Corrections to intra-frequency event triggered test cases (Rel 16) |
Rohde & Schwarz |
R4-2203604 |
Draft CR to TS 38.133: Corrections to intra-frequency event triggered test cases (Rel 17) |
Rohde & Schwarz |
R4-2203802 |
Draft CR on performance part maintenance for TS38.133 R15 |
Apple |
R4-2203803 |
Draft CR on performance part maintenance for TS38.133 R16 |
Apple |
R4-2203804 |
Draft CR on performance part maintenance for TS38.133 R17 |
Apple |
R4-2203831 |
draft Cat-F CR (R15) to PDSCH RMC |
Qualcomm Incorporated |
R4-2203832 |
draft Cat-A CR (R16) to PDSCH RMC |
Qualcomm Incorporated |
R4-2203833 |
draft Cat-A CR (R17) to PDSCH RMC |
Qualcomm Incorporated |
R4-2203834 |
draft Cat-F CR (R15) to E-UTRAN - NR FR2 interruptions at transitions between active and non-active during DRX in Xsynchronous EN-DC A.5.5.2.x |
Qualcomm Incorporated |
R4-2203835 |
draft Cat-A CR (R16) to E-UTRAN - NR FR2 interruptions at transitions between active and non-active during DRX in Xsynchronous EN-DC A.5.5.2.x |
Qualcomm Incorporated |
R4-2203836 |
draft Cat-A CR (R17) to E-UTRAN - NR FR2 interruptions at transitions between active and non-active during DRX in Xsynchronous EN-DC A.5.5.2.x |
Qualcomm Incorporated |
R4-2203840 |
draft Cat-F CR (R15) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2203841 |
draft Cat-A CR (R16) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2203842 |
draft Cat-A CR (R17) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2203892 |
Draft CR on radio link monitoring test cases |
CATT |
R4-2203893 |
Draft CR on radio link monitoring test cases |
CATT |
R4-2203894 |
Draft CR on radio link monitoring test cases |
CATT |
R4-2204371 |
CR for the RRC based BWP switch test case in EN-DC for R15 |
MediaTek Inc. |
R4-2204372 |
CR for the RRC based BWP switch test case in EN-DC for R16 |
MediaTek Inc. |
R4-2204373 |
CR for the RRC based BWP switch test case in EN-DC for R17 |
MediaTek Inc. |
R4-2204374 |
Discussion on FR2 inter-frequency relative RSRP accuracy |
MediaTek Inc. |
R4-2204844 |
Correction of R15 FR1 test cases and RMCs_R15 |
Huawei, Hisilicon |
R4-2204845 |
Correction of R15 FR1 test cases and RMCs_R16 |
Huawei, Hisilicon |
R4-2204846 |
Correction of R15 FR1 test cases and RMCs_R17 |
Huawei, Hisilicon |
R4-2204847 |
Correction of R15 FR2 test cases and RMCs_R15 |
Huawei, Hisilicon |
R4-2204848 |
Correction of R15 FR2 test cases and RMCs_R16 |
Huawei, Hisilicon |
R4-2204849 |
Correction of R15 FR2 test cases and RMCs_R17 |
Huawei, Hisilicon |
R4-2204856 |
Discussion on test cases maintenance |
Huawei, Hisilicon |
R4-2205073 |
draft CR: Correction of SA RRC re-establishment tests in FR2 Rel-15 |
Ericsson |
R4-2205074 |
draft CR: Correction of SA RRC re-establishment tests in FR2 Rel-16 |
Ericsson |
R4-2205075 |
draft CR: Correction of SA RRC re-establishment tests in FR2 Rel-16 |
Ericsson |
R4-2206803 |
Reduction of allocated RBs for CSI-RS based RLM TC in FR2 |
Anritsu Corporation |
R4-2206804 |
Reduction of allocated RBs for CSI-RS based RLM TC in FR2 |
Anritsu Corporation |
R4-2206805 |
Reduction of allocated RBs for CSI-RS based RLM TC in FR2 |
Anritsu Corporation |
R4-2206806 |
Correction on the FR2 inter-frequency relative RSRP accuracy |
Anritsu Corporation, MediaTek Inc. |
R4-2206807 |
Draft CR to maintain performance requirement |
Anritsu Corporation |
R4-2206808 |
Draft CR to TS 38.133: Corrections to active TCI state switch test cases (Rel 15) |
Rohde & Schwarz |
R4-2206809 |
Draft CR to TS 38.133: Corrections to intra-frequency event triggered test cases (Rel 15) |
Rohde & Schwarz |
R4-2206810 |
Draft CR on performance part maintenance for TS38.133 R15 |
Apple |
R4-2206811 |
draft Cat-F CR (R15) to PDSCH RMC |
Qualcomm Incorporated |
R4-2206812 |
draft Cat-F CR (R15) to E-UTRAN - NR FR2 interruptions at transitions between active and non-active during DRX in Xsynchronous EN-DC A.5.5.2.x |
Qualcomm Incorporated |
R4-2206813 |
draft Cat-F CR (R15) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2206815 |
Correction of R15 FR2 test cases and RMCs_R15 |
Huawei, Hisilicon |
R4-2206844 |
Draft CR on number of UL CC support for FR2 and interruption requirements for FR2 UL CA for IBM UE |
Ericsson |
R4-2207136 |
Big CR to TS 38.133: NR_newRAT-Perf maintenance (Rel-15) |
MCC, Ericsson |
R4-2207137 |
Big CR to TS 38.133: NR_newRAT-Perf maintenance (Rel-16) |
MCC, Ericsson |
R4-2207138 |
Big CR to TS 38.133: NR_newRAT-Perf maintenance (Rel-17) |
MCC, Ericsson |
R4-2207540 |
Big CR to TS 38.133: NR_newRAT-Perf maintenance (Rel-15) |
MCC, Ericsson |
R4-2207541 |
Big CR to TS 38.133: NR_newRAT-Perf maintenance (Rel-16) |
MCC, Ericsson |
R4-2207542 |
Big CR to TS 38.133: NR_newRAT-Perf maintenance (Rel-17) |
MCC, Ericsson |
4.1.8.1 |
UE demodulation requirements |
|
R4-2205779 |
CR:Updates to test setup for PDSCH and PDCCH requirements in TS 38.101-4 (Rel-15) |
Huawei,HiSilicon |
R4-2205780 |
CR:Updates to test setup for PDSCH and PDCCH requirements in TS 38.101-4 (Rel-16) |
Huawei,HiSilicon |
R4-2205781 |
CR:Updates to test setup for PDSCH and PDCCH requirements in TS 38.101-4 (Rel-17) |
Huawei,HiSilicon |
R4-2207147 |
Email discussion summary for [102-e][317] Demod_Maintenance_UE |
Moderator (Apple) |
R4-2207255 |
CR:Updates to test setup for PDSCH and PDCCH requirements in TS 38.101-4 (Rel-15) |
Huawei,HiSilicon |
R4-2207420 |
Email discussion summary for [102-e][317] Demod_Maintenance_UE |
Moderator (Apple) |
4.1.8.2 |
CSI requirements |
|
R4-2205100 |
draft CR: Correction of TBS for CQI reporting tests |
Ericsson |
R4-2205101 |
draft CR: Correction of TBS for CQI reporting tests |
Ericsson |
R4-2205102 |
draft CR: Correction of TBS for CQI reporting tests |
Ericsson |
R4-2205782 |
CR:Updates to test setup for CSI requirements in TS 38.101-4 (Rel-15) |
Huawei,HiSilicon |
R4-2205783 |
CR:Updates to test setup for CSI requirements in TS 38.101-4 (Rel-16) |
Huawei,HiSilicon |
R4-2205784 |
CR:Updates to test setup for CSI requirements in TS 38.101-4 (Rel-17) |
Huawei,HiSilicon |
R4-2207256 |
CR:Updates to test setup for CSI requirements in TS 38.101-4 (Rel-16) |
Huawei,HiSilicon |
4.1.8.3 |
BS demodulation requirements |
|
R4-2205734 |
Draft CR on correction to multi-slot PUCCH performance requirements (TS38.141-1, Rel-15) |
Huawei,HiSilicon |
R4-2205735 |
Draft CR on correction to multi-slot PUCCH performance requirements (TS38.141-1, Rel-16) |
Huawei,HiSilicon |
R4-2205736 |
Draft CR on correction to multi-slot PUCCH performance requirements (TS38.141-1, Rel-17) |
Huawei,HiSilicon |
R4-2205737 |
Draft CR on correction to manufactor declaration reference for PRACH formats (TS38.141-2, Rel-15) |
Huawei,HiSilicon |
R4-2205738 |
Draft CR on correction to manufactor declaration reference for PRACH formats (TS38.141-2, Rel-16) |
Huawei,HiSilicon |
R4-2205739 |
Draft CR on correction to manufactor declaration reference for PRACH formats (TS38.141-2, Rel-17) |
Huawei,HiSilicon |
R4-2207148 |
Email discussion summary for [102-e][316] Demod_Maintenance_BS |
Moderator (ZTE) |
R4-2207261 |
Draft CR on correction to multi-slot PUCCH performance requirements (TS38.141-1, Rel-15) |
Huawei,HiSilicon |
R4-2207421 |
Email discussion summary for [102-e][316] Demod_Maintenance_BS |
Moderator (ZTE) |
4.2.1 |
UE RF requirements |
|
R4-2205307 |
Draft CR for 36.101 to clarify the restriction of band 28 for CA_20-28(R14) |
Huawei, HiSilicon |
R4-2205308 |
Draft CR for 36.101 to clarify the restriction of band 28 for CA_20-28(R15) |
Huawei, HiSilicon |
R4-2205309 |
Draft CR for 36.101 to clarify the restriction of band 28 for CA_20-28(R16) |
Huawei, HiSilicon |
R4-2205310 |
Draft CR for 36.101 to clarify the restriction of band 28 for CA_20-28(R17) |
Huawei, HiSilicon |
R4-2205662 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2205663 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2205664 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2205665 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
R4-2206292 |
Draft CR for 36.101 Correction to Bands for NB-IoT in the USA |
Dish Network |
4.2.2 |
BS RF requirements |
|
R4-2204437 |
Draft CR to 36.104: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2204438 |
Draft CR to 36.104: BS OBUE requirements clarification, rel-16 |
NEC |
R4-2204439 |
Draft CR to 36.104: BS OBUE requirements clarification, rel-17 |
NEC |
R4-2204440 |
Draft CR to 36.141: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2204441 |
Draft CR to 36.141: BS OBUE requirements clarification, rel-16 |
NEC |
R4-2204442 |
Draft CR to 36.141: BS OBUE requirements clarification, rel-17 |
NEC |
R4-2207312 |
Draft CR to 36.141: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2207313 |
Draft CR to 36.104: BS OBUE requirements clarification, rel-15 |
NEC |
R4-2207465 |
Big CR for TS 36.104 Maintenance (Rel-15, CAT F) |
MCC, CATT |
R4-2207466 |
Big CR for TS 36.104 Maintenance (Rel-16, CAT A) |
MCC, CATT |
R4-2207467 |
Big CR for TS 36.104 Maintenance (Rel-17, CAT A) |
MCC, CATT |
R4-2207468 |
Big CR for TS 36.141 Maintenance (Rel-15, CAT F) |
MCC,S amsung |
R4-2207469 |
Big CR for TS 36.141 Maintenance (Rel-16, CAT A) |
MCC, Samsung |
R4-2207470 |
Big CR for TS 36.141 Maintenance (Rel-17, CAT F) |
MCC, Samsung |
R4-2207527 |
Big CR for TS 36.104 Maintenance (Rel-15, CAT F) |
MCC, CATT |
R4-2207528 |
Big CR for TS 36.104 Maintenance (Rel-16, CAT A) |
MCC, CATT |
R4-2207529 |
Big CR for TS 36.104 Maintenance (Rel-17, CAT A) |
MCC, CATT |
4.2.3 |
RRM requirements |
|
R4-2203725 |
CR: Correction on SyncRef UE Frequency Offset in Synchronization Reference Selection/Reselection Test |
Qualcomm, Inc. |
R4-2203726 |
(mirror R15)CR: Correction on SyncRef UE Frequency Offset in Synchronization Reference Selection/Reselection Test |
Qualcomm, Inc. |
R4-2203727 |
(mirror R16)CR: Correction on SyncRef UE Frequency Offset in Synchronization Reference Selection/Reselection Test |
Qualcomm, Inc. |
R4-2203728 |
(mirror R17)CR: Correction on SyncRef UE Frequency Offset in Synchronization Reference Selection/Reselection Test |
Qualcomm, Inc. |
R4-2203731 |
CR: Correction on Synchronization Reference Selection/Reselection SyncRefUE Frequency Offset Side Condition for LTE-V2X |
Qualcomm, Inc. |
R4-2203732 |
(mirro R15)CR: Correction on Synchronization Reference Selection/Reselection SyncRefUE Frequency Offset Side Condition for LTE-V2X |
Qualcomm, Inc. |
R4-2203733 |
(mirro R16)CR: Correction on Synchronization Reference Selection/Reselection SyncRefUE Frequency Offset Side Condition for LTE-V2X |
Qualcomm, Inc. |
R4-2203734 |
(mirro R17)CR: Correction on Synchronization Reference Selection/Reselection SyncRefUE Frequency Offset Side Condition for LTE-V2X |
Qualcomm, Inc. |
R4-2205347 |
CR to eMTC inter-frequency measurement requirements in Idle mode R14 |
Huawei, HiSilicon |
R4-2205348 |
CR to eMTC inter-frequency measurement requirements in Idle mode R15 |
Huawei, HiSilicon |
R4-2205349 |
CR to eMTC inter-frequency measurement requirements in Idle mode R16 |
Huawei, HiSilicon |
R4-2205350 |
CR to eMTC inter-frequency measurement requirements in Idle mode R17 |
Huawei, HiSilicon |
R4-2206750 |
Email discussion summary for [102-e][207] Maintenance_LTE_RRM |
Moderator (Ericsson) |
R4-2206816 |
CR: Correction on Synchronization Reference Selection/Reselection SyncRefUE Frequency Offset Side Condition for NR-V2X |
Qualcomm, Inc. |
R4-2206832 |
CR: Correction on Synchronization Reference Selection/Reselection SyncRefUE Frequency Offset Side Condition for LTE-V2X |
Qualcomm, Inc. |
R4-2206833 |
CR to eMTC inter-frequency measurement requirements in Idle mode R14 |
Huawei, HiSilicon |
R4-2207048 |
Email discussion summary for [102-e][207] Maintenance_LTE_RRM |
Moderator (Ericsson) |
R4-2207129 |
Big CR to TS 36.133: LTE RRM maintenance (Rel-14) |
MCC, Huawei |
R4-2207130 |
Big CR to TS 36.133: LTE RRM maintenance (Rel-15) |
MCC, Huawei |
R4-2207131 |
Big CR to TS 36.133: LTE RRM maintenance (Rel-16) |
MCC, Huawei |
R4-2207132 |
Big CR to TS 36.133: LTE RRM maintenance (Rel-17) |
MCC, Huawei |
4.2.4.1 |
UE demodulation and CSI requirements |
|
R4-2203617 |
Correction to Cat1bis RMCs |
Rohde & Schwarz |
R4-2203618 |
Correction to Cat1bis RMCs |
Rohde & Schwarz |
R4-2203619 |
Correction to Cat1bis RMCs |
Rohde & Schwarz |
R4-2203620 |
Correction to Cat1bis RMCs |
Rohde & Schwarz |
R4-2205785 |
CR: Updates to NPDSCH repetition number for LTE NPDSCH requirements with multi-TB interleaved transmission (Rel-16) |
Huawei,HiSilicon |
R4-2205786 |
CR: Updates to NPDSCH repetition number for LTE NPDSCH requirements with multi-TB interleaved transmission (Rel-17) |
Huawei,HiSilicon |
5.1 |
NR WIs and TEI |
|
R4-2206626 |
Big CR for TS 38.101-1 Maintenance Part-2 (Rel-16) |
MCC, VIVO |
R4-2206627 |
Big CR for TS 38.101-1 Maintenance Part-2 (Rel-17) |
MCC, VIVO |
5.1.1.1 |
System parameter |
|
R4-2203613 |
Correction to n46 channel raster |
Rohde & Schwarz |
R4-2203614 |
Correction to n46 channel raster |
Rohde & Schwarz |
R4-2203615 |
Correction to n46 channel raster |
Rohde & Schwarz |
R4-2203616 |
Correction to n46 channel raster |
Rohde & Schwarz |
R4-2204602 |
Correction to the note on the use of operating bands for shared spectrum access |
Ericsson |
R4-2204603 |
Correction to the note on the use of operating bands for shared spectrum access |
Ericsson |
R4-2206302 |
Email discussion summary for [102-e][102] R16_Maintenance |
Moderator (OPPO) |
R4-2206344 |
WF on Intra-band EN-DC Support |
Xiaomi |
R4-2206402 |
Email discussion summary for [102-e][102] R16_Maintenance |
Moderator (OPPO) |
5.1.1.3 |
RRM requirements |
|
R4-2203522 |
Correction of NR-U inter-frequency cell identification and measurements requirements |
Nokia, Nokia Shanghai Bell |
R4-2203523 |
Correction of NR-U inter-frequency cell identification and measurements requirements |
Nokia, Nokia Shanghai Bell |
R4-2203524 |
Correction of inter-frequency measurement procedures TCs under CCA |
Nokia, Nokia Shanghai Bell |
R4-2203525 |
Correction of inter-frequency measurement procedures TCs under CCA |
Nokia, Nokia Shanghai Bell |
R4-2203526 |
Removal of TCI state switching TC for unlicensed bands |
Nokia, Nokia Shanghai Bell |
R4-2203527 |
Removal of TCI state switching TC for unlicensed bands |
Nokia, Nokia Shanghai Bell |
R4-2203845 |
draft Cat-F CR (R16) to SCell Activation Core NR-U |
Qualcomm Incorporated |
R4-2203846 |
draft Cat-A CR (R17) to SCell Activation Core NR-U |
Qualcomm Incorporated |
R4-2203849 |
draft Cat-F CR (R16) to SCell Activation Test Cases NR-U |
Qualcomm Incorporated |
R4-2203850 |
draft Cat-A CR (R17) to SCell Activation Test Cases NR-U |
Qualcomm Incorporated |
R4-2204857 |
Draft CR on maintenance of measurement requirements for NR-U R16 |
Huawei, Hisilicon |
R4-2204858 |
Draft CR on maintenance of measurement requirements for NR-U R17 |
Huawei, Hisilicon |
R4-2204859 |
Draft CR on TC of BFD and CBD for NR-U R16 |
Huawei, Hisilicon |
R4-2204860 |
Draft CR on TC of BFD and CBD for NR-U R17 |
Huawei, Hisilicon |
R4-2204861 |
Draft CR on TC of inter-RAT measurement procedure for NR-U R16 |
Huawei, Hisilicon |
R4-2204862 |
Draft CR on TC of inter-RAT measurement procedure for NR-U R17 |
Huawei, Hisilicon |
R4-2204863 |
Draft CR on TC of inter-RAT SFTD measurement procedure for NR-U R16 |
Huawei, Hisilicon |
R4-2204864 |
Draft CR on TC of inter-RAT SFTD measurement procedure for NR-U R17 |
Huawei, Hisilicon |
R4-2204865 |
Draft CR on TC of intra-frequency measurement accuracy for NR-U R16 |
Huawei, Hisilicon |
R4-2204866 |
Draft CR on TC of intra-frequency measurement accuracy for NR-U R17 |
Huawei, Hisilicon |
R4-2204867 |
Draft CR on TC of RLM for NR-U R16 |
Huawei, Hisilicon |
R4-2204868 |
Draft CR on TC of RLM for NR-U R17 |
Huawei, Hisilicon |
R4-2205076 |
Draft CR: Clarification of availability of SSB monitoring occasions for RLM and BM |
Ericsson |
R4-2205077 |
Draft CR: Clarification of availability of SSB monitoring occasions for RLM and BM |
Ericsson |
R4-2205078 |
Draft CR: Addition of SS-SINR/SS-RSRQ measurement accuracy tests for NR-U |
Ericsson |
R4-2205079 |
Draft CR: Addition of SS-SINR/SS-RSRQ measurement accuracy tests for NR-U |
Ericsson |
R4-2205522 |
Remaining issues on cell selection in Idle mode for NR-U |
Ericsson |
R4-2205523 |
draftCR on cell selection in Idle mode for NR-U -r16 |
Ericsson |
R4-2205524 |
draftCR on cell selection in Idle mode for NR-U -r17 |
Ericsson |
R4-2207044 |
Email discussion summary for [102-e][203] Maintenance_NR_unlic |
Moderator (Nokia) |
R4-2207085 |
WF on RRM requirements Rel 16 NR_unlic maintenance |
Nokia, Nokia Shanghai Bell |
R4-2207099 |
draft Cat-F CR (R16) to SCell Activation Core NR-U |
Qualcomm Incorporated |
R4-2207100 |
draft Cat-F CR (R16) to SCell Activation Test Cases NR-U |
Qualcomm Incorporated |
5.1.1.4 |
Others |
|
R4-2203643 |
Draft CR to TS 37.105 on correction of OTA blocking requirement for co-location with MR BS in NR band n96 |
Nokia, Nokia Shanghai Bell |
R4-2203644 |
Draft CR to TS 37.105 on correction of OTA blocking requirement for co-location with MR BS in NR band n96 |
Nokia, Nokia Shanghai Bell |
R4-2205196 |
Draft CR to 38.104 with addition of absolute values to NR-U masks and clarifications for NR-U bands |
Nokia, Nokia Shanghai Bell |
R4-2205197 |
Draft CR to 38.104 with addition of absolute values to NR-U masks and clarifications for NR-U bands |
Nokia, Nokia Shanghai Bell |
R4-2205198 |
Draft CR to 38.141-1 with addition of absolute values to NR-U masks and clarifications for NR-U bands |
Nokia, Nokia Shanghai Bell |
R4-2205199 |
Draft CR to 38.141-1 with addition of absolute values to NR-U masks and clarifications for NR-U bands |
Nokia, Nokia Shanghai Bell |
R4-2205200 |
Draft CR to 38.141-2 with clarifications of BS type 1-O requirements for NR-U bands |
Nokia, Nokia Shanghai Bell |
R4-2205201 |
Draft CR to 38.141-2 with clarifications of BS type 1-O requirements for NR-U bands |
Nokia, Nokia Shanghai Bell |
R4-2205787 |
CR: Updates to interlace index for interlaced PF0 and PF1 requirements in TS 38.104 (Rel-16) |
Huawei,HiSilicon |
R4-2205957 |
Editorial CR for NR-U demod requiremetns for 2RX |
Apple |
R4-2207454 |
CR: Updates to interlace index for interlaced PF0 and PF1 requirements in TS 38.104 (Rel-17) |
Huawei,HiSilicon |
5.1.2.1 |
RRM requirements |
|
R4-2203573 |
Consideration on MAC-CE based PL-RS switching delay TCs |
Anritsu Corporation |
R4-2204694 |
Draft CR to TS38.133 Corrections on L1-SINR requirement (Rel-16) |
Samsung |
R4-2204695 |
Draft CR to TS38.133 Corrections on L1-SINR requirement (Rel-17) |
Samsung |
R4-2205317 |
Discussion on maintaining PL-RS switching delay requirements in R16 |
Huawei, HiSilicon |
R4-2205318 |
DraftCR on maintaining PL-RS switching delay requirements R16 |
Huawei, HiSilicon |
R4-2205319 |
DraftCR on maintaining PL-RS switching delay requirements R17 |
Huawei, HiSilicon |
R4-2205320 |
DraftCR on correction to L1-SINR and SCell BFR tests R16 |
Huawei, HiSilicon |
R4-2205321 |
DraftCR on correction to L1-SINR and SCell BFR tests R17 |
Huawei, HiSilicon |
R4-2205411 |
On defining test cases for PL RS activation delay |
ZTE Corporation |
R4-2205412 |
[dCR] Test cases for applicable timing for PL RS activated by MAC-CE |
ZTE Corporation, Anritsu Corporation |
R4-2205413 |
[dCR] Test cases for applicable timing for PL RS activated by MAC-CE |
ZTE Corporation, Anritsu Corporation |
R4-2206747 |
Email discussion summary for [102-e][204] Maintenance_NR_eMIMO |
Moderator (Samsung) |
R4-2206748 |
Email discussion summary for [102-e][205] Maintenance_NR_pos |
Moderator (Intel) |
R4-2206820 |
WF on eMIMO RRM Maintenance |
Samsung |
R4-2207045 |
Email discussion summary for [102-e][204] Maintenance_NR_eMIMO |
Moderator (Samsung) |
R4-2207086 |
[dCR] Test cases for applicable timing for PL RS activated by MAC-CE |
ZTE Corporation, Anritsu Corporation |
R4-2207089 |
DraftCR on maintaining PL-RS switching delay requirements R16 |
Huawei, HiSilicon |
R4-2207113 |
[dCR] Test cases for applicable timing for PL RS activated by MAC-CE |
ZTE Corporation, Anritsu Corporation |
5.1.2.2 |
Demodulation performance requirements |
|
R4-2205909 |
Draft CR to TS38.101-4, Correction to reference channels for PDSCH requirements with single-DCI based FDM Scheme A (Rel-16) |
MediaTek inc. |
R4-2205910 |
Draft CR to TS38.101-4, Correction to reference channels for PDSCH requirements with single-DCI based FDM Scheme A (Rel-17) |
MediaTek inc. |
5.1.3 |
NR Positioning Support |
|
R4-2206821 |
WF on maintenance to R16 POS requirements |
Intel Corporation, Qualcomm |
5.1.3.1 |
RRM core requirement |
|
R4-2203869 |
Discussion on R16 NR positioning core requirement maintenance |
CATT |
R4-2203870 |
Draft CR on R16 NR positioning measurement requirements |
CATT |
R4-2203871 |
Draft CR on R16 NR positioning measurement requirements |
CATT |
R4-2204461 |
Remaining issues in NR positioning core requirements |
Qualcomm Incorporated |
R4-2204652 |
Remaining issues on measurement requirements for Rel-16 NR positioning |
vivo |
R4-2204654 |
Draft CR to 38.133 correction to NR positioning measurement requirements |
vivo |
R4-2204655 |
Draft CR to 38.133 correction to NR positioning measurement requirements |
vivo |
R4-2205351 |
Discussion on remaining issues for positioning measurement requirements |
Huawei, HiSilicon |
R4-2205352 |
CR on positioning measurement requirements R16 |
Huawei, HiSilicon |
R4-2205353 |
CR on positioning measurement requirements R17 |
Huawei, HiSilicon |
R4-2206031 |
On UE positioning measurement requirements |
Ericsson |
R4-2206032 |
Updates to measurement requirements for UE positioning measurements in TS 38.133 |
Ericsson |
R4-2206033 |
Updates to measurement requirements for UE positioning measurements in TS 38.133 |
Ericsson |
R4-2206822 |
Draft CR on R16 NR positioning measurement requirements |
CATT |
R4-2207046 |
Email discussion summary for [102-e][205] Maintenance_NR_pos |
Moderator (Intel) |
5.1.3.2 |
RRM performance requirements |
|
R4-2203872 |
Discussion on R16 NR positioning performance maintenance |
CATT |
R4-2203873 |
Draft CR on R16 NR positioning accuracy requirements |
CATT |
R4-2203874 |
Draft CR on R16 NR positioning accuracy requirements |
CATT |
R4-2203875 |
Draft CR on SRS configuration for R16 positioning test case |
CATT |
R4-2203876 |
Draft CR on SRS configuration for R16 positioning test case |
CATT |
R4-2204407 |
Discussion on Rel-16 NR positioning measurement accuracy requirements |
Intel Corporation |
R4-2204462 |
On UE measurement accuracy requirements for NR positioning |
Qualcomm Incorporated |
R4-2204653 |
Remaining issues on measurement accuracy requirements for Rel-16 NR positioning |
vivo |
R4-2204656 |
Draft CR to 38.133 correction to NR positioning accuracy requirements |
vivo |
R4-2204657 |
Draft CR to 38.133 correction to NR positioning accuracy requirements |
vivo |
R4-2205354 |
Discussion on accuracy requirements for positioning measurement |
Huawei, HiSilicon |
R4-2205355 |
CR on accuracy requirements for positioning measurement R16 |
Huawei, HiSilicon |
R4-2205356 |
CR on accuracy requirements for positioning measurement R17 |
Huawei, HiSilicon |
R4-2205357 |
CR to introduce posSRS RMC for positioning test cases R16 |
Huawei, HiSilicon |
R4-2205358 |
CR to introduce posSRS RMC for positioning test cases R17 |
Huawei, HiSilicon |
R4-2205441 |
On UE-based DL-TDOA support |
Rohde & Schwarz |
R4-2205442 |
Draft CR to TS 38.133: Additions to RSTD test cases for UE-based DL-TDOA support (Rel 16) |
Rohde & Schwarz |
R4-2205443 |
Draft CR to TS 38.133: Additions to RSTD test cases for UE-based DL-TDOA support (Rel 17) |
Rohde & Schwarz |
R4-2206034 |
On UE positioning accuracy measurements |
Ericsson |
R4-2206035 |
Updates to accuracy requirements for UE positioning measurements in TS 38.133 |
Ericsson |
R4-2206036 |
Updates to accuracy requirements for UE positioning measurements in TS 38.133 |
Ericsson |
R4-2206823 |
Draft CR on SRS configuration for R16 positioning test case |
CATT |
R4-2206824 |
Draft CR to 38.133 correction to NR positioning accuracy requirements |
vivo |
R4-2206825 |
CR on accuracy requirements for positioning measurement R16 |
Huawei, HiSilicon |
R4-2206826 |
Updates to accuracy requirements for UE positioning measurements in TS 38.133 |
Ericsson |
5.1.4 |
NR RRM requirements for CSI-RS based L3 measurement |
|
R4-2204708 |
Open issues on CSI-RS based measurement requirements |
Nokia, Nokia Shanghai Bell |
R4-2204709 |
38.133 draftCR on CSI-RS based measurements reporting requirements |
Nokia, Nokia Shanghai Bell |
R4-2204710 |
38.133 draftCR on CSI-RS based measurements reporting requirements |
Nokia, Nokia Shanghai Bell |
R4-2205359 |
Discussion on remaining issue in CSI-RS core requirements |
Huawei, HiSilicon |
R4-2205360 |
CR on CSI-RS measurement requirements R16 |
Huawei, HiSilicon |
R4-2205361 |
CR on CSI-RS measurement requirements R17 |
Huawei, HiSilicon |
R4-2205655 |
Draft CR on CSI-RS L3 measurement capability for TS36.133 R16 |
Apple |
R4-2205656 |
Draft CR on CSI-RS L3 measurement capability for TS36.133 R17 |
Apple |
R4-2206749 |
Email discussion summary for [102-e][206] Maintenance_NR_CSIRS_L3meas |
Moderator (CATT) |
R4-2206827 |
WF on CSI-RS based L3 measurement
requirements |
CATT |
R4-2206828 |
LS on the applicability of mixed numerology on UE capability maxNumberCSI-RS-RRM-RS-SINR |
Apple |
R4-2206829 |
38.133 draftCR on CSI-RS based measurements reporting requirements |
Nokia, Nokia Shanghai Bell |
R4-2207047 |
Email discussion summary for [102-e][206] Maintenance_NR_CSIRS_L3meas |
Moderator (CATT) |
5.1.5 |
Other NR WIs and Rel-16 NR TEI |
|
R4-2207497 |
Big CR for TS 38.174 Maintenance (Rel-16, CAT F) |
MCC, CATT |
R4-2207498 |
Big CR for TS 38.176-1 Maintenance (Rel-16, CAT F) |
MCC, Huawei |
R4-2207499 |
Big CR for TS 38.176-2 Maintenance (Rel-16, CAT F) |
MCC, Nokia |
R4-2207500 |
Big CR for TR 38.809 Maintenance (Rel-16, CAT F) |
MCC, Samsung |
5.1.5.1 |
BS RF requirements |
|
R4-2203645 |
Draft CR to TR 38.809 on clarification and correction of conformance testing aspects |
Nokia, Nokia Shanghai Bell, Samsung |
R4-2203933 |
Draft CR for TS 38.174: Update the co-existence and co-location tables to include missing bands |
CATT |
R4-2203934 |
Draft CR for TS 38.176-1: Update the co-existence and co-location tables to include missing bands |
CATT |
R4-2203935 |
Draft CR for TS 38.176-2: Update the co-existence and co-location tables to include missing bands |
CATT |
R4-2204577 |
Draft CR for clean-up to 38.176-1 |
Samsung |
R4-2204578 |
Draft CR for clean-up to 38.176-2 |
Samsung |
R4-2205852 |
TS 38.175: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207182 |
TS 38.175: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207183 |
TS 36.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2207184 |
TS 37.113: Corrections in clause 9 Immunity |
Ericsson |
R4-2207185 |
TS 37.114: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207186 |
TS 38.113: Corrections in clause 1 Scope and clause 9 Immunity |
Ericsson |
R4-2207311 |
Draft CR for TS 38.176-2: Update the co-existence and co-location tables to include missing bands |
CATT |
5.1.5.2 |
UE RF requirements |
|
R4-2204065 |
draft CR to TS 38.307 on Release independence of FDD-TDD EN-DC High Power UE |
CHTTL, China Unicom, ZTE |
R4-2204066 |
draft CR to TS 38.307 on Release independence of FDD-TDD EN-DC High Power UE |
CHTTL, China Unicom, ZTE |
R4-2206573 |
Draft CR to TS38.101-1: Corrections on REFSEN for CA |
ZTE |
5.1.5.2.1 |
FR1 38.101-1 |
|
R4-2203676 |
draftCR to 38.101-1 on new NS for Canadian WCS regulation R16 |
Apple |
R4-2203677 |
draftCR to 38.101-1 on new NS for Canadian WCS regulation R17 |
Apple |
R4-2203686 |
On Transient period capability |
Apple |
R4-2203687 |
Discussion on Rel-16 guard period for SRS antenna switching |
Apple |
R4-2204199 |
n1 and n65 coexistence fix CR Cat-F rel 16 |
Qualcomm Incorporated |
R4-2204200 |
n1 and n65 coexistence fix CR Cat-A rel 17 |
Qualcomm Incorporated |
R4-2204201 |
AMPR rel 16 fixes from previous endorsed CRs and inequality fix Cat-A rel 16 |
Qualcomm Incorporated |
R4-2204202 |
AMPR rel 16 fixes from previous endorsed CRs and inequality fix Cat-A rel 17 |
Qualcomm Incorporated |
R4-2204208 |
n65 AMPR discrepancies rel 16 CR Cat-F rel 16 |
Qualcomm Incorporated |
R4-2204209 |
n65 AMPR discrepancies rel 16 CR Cat-A rel 17 |
Qualcomm Incorporated |
R4-2204210 |
n65 AMPR discrepancies |
Qualcomm Incorporated |
R4-2204512 |
Draft CR to 38.101-1 Correction on UE maximum output power for intra-band CA (R16) |
China Telecom Corporation Ltd. |
R4-2204518 |
Short Transient Period |
Qualcomm Incorporated |
R4-2204521 |
n65 AMPR corrections rel 16 CR Cat-F rel 16 |
Qualcomm Incorporated |
R4-2204737 |
Draft CR to TS38.101-1: Corrections on REFSEN for CA |
ZTE Corporation |
R4-2204738 |
Draft CR to TS38.101-1: Corrections on REFSEN for CA |
ZTE Corporation |
R4-2204823 |
On transient period capability |
Huawei, HiSilicon |
R4-2205184 |
Draft CR for 38.101-1 updating note in MSD tables (Rel-16) |
Huawei, HiSilicon |
R4-2205185 |
Draft CR for 38.101-1 updating note in MSD tables (Rel-17) |
Huawei, HiSilicon |
R4-2205186 |
Draft CR for 38.101-1 updating references in V2X test cases (Rel-16) |
Huawei, HiSilicon |
R4-2205187 |
Draft CR for 38.101-1 updating references in V2X test cases (Rel-17) |
Huawei, HiSilicon |
R4-2205297 |
Draft CR for 38.101-1 to correct configured transmit power for V2X(R16) |
Huawei, HiSilicon |
R4-2205298 |
Draft CR for 38.101-1 to correct configured transmit power for V2X(R17) |
Huawei, HiSilicon |
R4-2205881 |
Corrections on carrier leakage requirement |
Qualcomm Incorporated |
R4-2206011 |
n30 NS for Canada Regulation |
Qualcomm Incorporated |
R4-2206093 |
Corrections on carrier leakage requirement |
Qualcomm Incoporated |
R4-2206125 |
CR to R16 TS38.101-1 on transient period capability |
Skyworks Solutions Inc. |
R4-2206345 |
Draft CR for 38.101-1 updating note in MSD tables (Rel-16) |
Huawei, HiSilicon |
R4-2206346 |
Draft CR for 38.101-1 updating references in V2X test cases (Rel-16) |
Huawei, HiSilicon |
R4-2206347 |
Corrections on carrier leakage requirement |
Qualcomm Incorporated |
R4-2206348 |
n65 AMPR discrepancies rel 16 CR Cat-F rel 16 |
Qualcomm Incorporated |
R4-2206349 |
CR to R16 TS38.101-1 on transient period capability |
Skyworks Solutions Inc. |
5.1.5.2.2 |
FR2 38.101-2 |
|
R4-2203611 |
Correction to Rel-16 FR2 RMCs |
Rohde & Schwarz |
R4-2203612 |
Correction to Rel-16 FR2 RMCs |
Rohde & Schwarz |
R4-2204739 |
Draft CR to TS38.101-2: Add default power class for NR inter-band CA combination |
ZTE Corporation |
R4-2204740 |
Draft CR to TS38.101-2: Add default power class for NR inter-band CA combination |
ZTE Corporation |
R4-2206350 |
Draft CR to TS38.101-2: Add default power class for NR inter-band CA combination |
ZTE Corporation |
5.1.5.2.3 |
Requirements for 38.101-3 |
|
R4-2203673 |
draftCR for TS 38.101-3 Rel-16: Corrections on UE co-existence |
Apple |
R4-2203674 |
draftCR for TS 38.101-3 Rel-17: Corrections on UE co-existence |
Apple |
R4-2203988 |
Draft CR to TS 38.307 on NR UE power class |
ZTE Corporation |
R4-2203989 |
Draft CR to TS 38.307 on NR UE power class (R17_CAT_A) |
ZTE Corporation |
R4-2203992 |
Draft CR to TS 38.307 on NR intra-band CA BW class within FR1 (Rel-16) |
ZTE Corporation |
R4-2203995 |
Draft CR to TS 38.101-3 on corrections to inter-band EN-DC configurations including FR1 and FR2 |
ZTE Corporation |
R4-2203996 |
Draft CR to TS 38.101-3 on corrections to inter-band EN-DC configurations including FR1 and FR2 (R17_CAT_A) |
ZTE Corporation |
R4-2204975 |
Resubmission of CR to TS 38.307 on Release independence of FDD-TDD EN-DC High Power UE |
vivo |
R4-2204976 |
Resubmission of CR to TS 38.307 on Release independence of FDD-TDD EN-DC High Power UE |
vivo |
R4-2205112 |
Discussion on intrabandENDC-Support |
Xiaomi |
R4-2205113 |
Draft CR for 38.101-3 Rel-16 to correct band combination for intra-band ENDC |
Xiaomi |
R4-2205114 |
Draft CR for 38.101-3 Rel-17 to correct band combination for intra-band ENDC |
Xiaomi |
R4-2205115 |
Draft CR for 38.101-3 Rel-16 to modify the notes and correct the configurations for inter-band EN-DC configurations |
Xiaomi |
R4-2205182 |
Draft CR for 38.101-3 updating note in MSD tables (Rel-16) |
Huawei, HiSilicon |
R4-2205183 |
Draft CR for 38.101-3 updating note in MSD tables (Rel-17) |
Huawei, HiSilicon |
R4-2205273 |
Draft CR for 38.101-3 to specify type 2 UE requirements(Rel-16) |
Huawei, HiSilicon |
R4-2205274 |
Draft CR for 38.101-3 to specify type 2 UE requirements(Rel-17) |
Huawei, HiSilicon |
R4-2205299 |
Draft CR for 38.101-3 to add MOP for band combination related to band 3C(R16) |
Huawei, HiSilicon |
R4-2205300 |
Draft CR for 38.101-3 to add MOP for band combination related to band 3C(R17) |
Huawei, HiSilicon |
R4-2205311 |
Draft CR for 38.101-3 to delete the MSD frequency test points for DC_1A_n5A(R16) |
Huawei, HiSilicon |
R4-2205312 |
Draft CR for 38.101-3 to delete the MSD frequency test points for DC_1A_n5A(R17) |
Huawei, HiSilicon |
R4-2205612 |
Draft CR to correct DC_3A_n38A test frequencies |
Anritsu Limited |
R4-2205613 |
Draft CR to correct DC_3A_n38A test frequencies |
Anritsu Limited |
R4-2205706 |
draft Rel-16 CR 38101-3-ga0 to align spurious emission between R15 and R16 |
Ericsson |
R4-2205879 |
Discussion on Intra-Band EN-DC support |
Google Inc. |
R4-2206009 |
draft CR for Type II UE Cat-F rel 16 |
Qualcomm Incorporated |
R4-2206010 |
draft CR for Type II UE Cat-A rel 17 |
Qualcomm Incorporated |
R4-2206351 |
Draft CR for 38.101-3 Rel-16 to modify the notes and correct the configurations for inter-band EN-DC configurations |
Xiaomi |
R4-2206352 |
Draft CR for 38.101-3 updating note in MSD tables (Rel-16) |
Huawei, HiSilicon |
R4-2206353 |
Draft CR for 38.101-3 to specify type 2 UE requirements(Rel-16) |
Huawei, HiSilicon |
5.1.5.3 |
RRM requirements |
|
R4-2207090 |
LS on UE capability for inter-frequency measurement without MG |
Huawei |
R4-2207139 |
Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 1 (Rel-16) |
MCC, vivo |
R4-2207140 |
Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 1 (Rel-17) |
MCC, vivo |
R4-2207141 |
Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 2 (Rel-16) |
MCC, Intel Corporation |
R4-2207142 |
Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 2 (Rel-17) |
MCC, Intel Corporation |
R4-2207143 |
Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 3 (Rel-16) |
MCC, OPPO |
R4-2207538 |
Big CR to TS 38.133: Rel-16 WIs RRM maintenance Part 3 (Rel-17) |
MCC, OPPO |
5.1.5.3.1 |
RRM core requirements |
|
R4-2203729 |
CR: Correction on Synchronization Reference Selection/Reselection SyncRefUE Frequency Offset Side Condition for NR-V2X |
Qualcomm, Inc. |
R4-2203730 |
(mirror R17)CR: Correction on Synchronization Reference Selection/Reselection SyncRefUE Frequency Offset Side Condition for NR-V2X |
Qualcomm, Inc. |
R4-2203797 |
Draft CR on core part maintenance for TS38.133 R16 |
Apple |
R4-2203798 |
Draft CR on core part maintenance for TS38.133 R17 |
Apple |
R4-2203843 |
draft Cat-F CR (R16) to SCell Activation Core |
Qualcomm Incorporated |
R4-2203844 |
draft Cat-A CR (R17) to SCell Activation Core |
Qualcomm Incorporated |
R4-2204158 |
Draft CR on EUTRAN-NR cell re-selection in HST |
CATT |
R4-2204159 |
Draft CR on EUTRAN-NR cell re-selection in HST |
CATT |
R4-2204311 |
Draft CR to maintain measurement gap sharing in TS 38.133 |
OPPO |
R4-2204312 |
Draft CR to maintain measurement gap sharing in TS 38.133 |
OPPO |
R4-2204347 |
Maintenance CR for RRM requirements on 38.133 R16 |
MediaTek (Shenzhen) Inc. |
R4-2204348 |
Maintenance CR for RRM requirements on 38.133 R17 |
MediaTek (Shenzhen) Inc. |
R4-2204349 |
Draft CR on SRVCC maintenance for TS36.133 R16 |
Apple |
R4-2204350 |
Draft CR on SRVCC maintenance for TS36.133 R17 |
Apple |
R4-2204426 |
Corrections to HST requirements in R16 |
Intel Corporation |
R4-2204427 |
Corrections to HST requirements in R16 |
Intel Corporation |
R4-2205322 |
DraftCR on correction on interruption requirements for IBM R16 |
Huawei, HiSilicon |
R4-2205323 |
DraftCR on correction on interruption requirements for IBM R17 |
Huawei, HiSilicon |
R4-2205362 |
CR on inter-frequency measurement without MG R16 |
Huawei, HiSilicon |
R4-2205363 |
CR on inter-frequency measurement without MG R17 |
Huawei, HiSilicon |
R4-2205364 |
CR on CBW change requirements R16 |
Huawei, HiSilicon |
R4-2205365 |
CR on CBW change requirements R17 |
Huawei, HiSilicon |
R4-2205405 |
draft CR to 38174 on antenna connectors and RIBs |
ZTE Corporation |
R4-2205644 |
Editorial correction to EN-DC interruption requirements |
Ericsson |
R4-2205828 |
Discussion on number of DL CC to be supported for FR2 |
Ericsson |
R4-2205829 |
Draft CR on number of DL CC in FR2 for IBM UE |
Ericsson |
R4-2206067 |
Discussion on number of serving carriers to be supported for FR2 |
Ericsson |
R4-2206068 |
Draft CR on number of serving carriers to be supported for FR2 in NR SA |
Ericsson |
R4-2206745 |
Email discussion summary for [102-e][202] Maintenance_NR_RRM |
Moderator (Apple) |
R4-2206746 |
Email discussion summary for [102-e][203] Maintenance_NR_unlic |
Moderator (Nokia) |
R4-2206817 |
Draft CR on SRVCC maintenance for TS36.133 R16 |
Apple |
R4-2206819 |
draft CR to 38174 on antenna connectors and RIBs |
ZTE Corporation |
R4-2207043 |
Email discussion summary for [102-e][202] Maintenance_NR_RRM |
Moderator (Apple) |
R4-2207091 |
draft CR to 38174 on antenna connectors and RIBs |
ZTE Corporation |
R4-2207094 |
DraftCR on correction on interruption requirements for IBM R16 |
Huawei, HiSilicon |
R4-2207095 |
CR on inter-frequency measurement without MG R16 |
Huawei, HiSilicon |
R4-2207096 |
Draft CR on number of serving carriers to be supported for FR2 in NR SA |
Ericsson |
R4-2207112 |
Draft CR on number of serving carriers to be supported for FR2 in NR SA |
Ericsson |
5.1.5.3.2 |
RRM performance requirements |
|
R4-2203528 |
Correction of 2-step RACH RRM performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2203529 |
Correction of 2-step RACH RRM performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2203574 |
Draft CR to maintain HST performance requirement |
Anritsu Corporation |
R4-2203575 |
Draft CR to maintain HST performance requirement |
Anritsu Corporation |
R4-2203723 |
CR: Correction on SyncRef UE Frequency Offset in Synchronization Reference Selection/Reselection Test |
Qualcomm, Inc. |
R4-2203724 |
(mirror R17)CR: Correction on SyncRef UE Frequency Offset in Synchronization Reference Selection/Reselection Test |
Qualcomm, Inc. |
R4-2203847 |
draft Cat-F CR (R16) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2203848 |
draft Cat-A CR (R17) to SCell Activation Test Cases |
Qualcomm Incorporated |
R4-2203895 |
Draft CR on TC for EUTRAN-NR cell re-selection in HST |
CATT |
R4-2203896 |
Draft CR on TC for EUTRAN-NR cell re-selection in HST |
CATT |
R4-2204369 |
CR for the number of ACK and NACK in CGI reading test case in NR SA for R16 |
MediaTek Inc. |
R4-2204370 |
CR for the number of ACK and NACK in CGI reading test case in NR SA for R17 |
MediaTek Inc. |
R4-2204850 |
Correction of NR Sidelink reference configurations_R16 |
Huawei, Hisilicon |
R4-2204851 |
Correction of NR Sidelink reference configurations_R17 |
Huawei, Hisilicon |
R4-2204852 |
Correction of NR Sidelink test cases_R16 |
Huawei, Hisilicon |
R4-2204853 |
Correction of NR Sidelink test cases_R17 |
Huawei, Hisilicon |
R4-2204854 |
Correction of mobility enhancement test cases_R16 |
Huawei, Hisilicon |
R4-2204855 |
Correction of mobility enhancement test cases_R17 |
Huawei, Hisilicon |
R4-2205366 |
CR to introduce EMR TC#5 R16 |
Huawei, HiSilicon |
R4-2205367 |
CR to introduce EMR TC#5 R17 |
Huawei, HiSilicon |
R4-2206818 |
Correction of NR Sidelink reference configurations_R16 |
Huawei, Hisilicon |
R4-2207092 |
Correction of NR Sidelink test cases_R16 |
Huawei, Hisilicon |
R4-2207093 |
Correction of mobility enhancement test cases_R16 |
Huawei, Hisilicon |
5.1.5.4.1 |
UE demodulation requirements |
|
R4-2205492 |
Draft CR on removing square brakets for CA demodulation test requirements (Rel-16) |
China Telecom |
R4-2205493 |
Draft CR on removing square brakets for CA demodulation test requirements (Rel-17) |
China Telecom |
R4-2205572 |
Draft CR on removing square brakets for CA demodulation test requirements (Rel-16) |
China Telecom |
R4-2205573 |
Draft CR on removing square brakets for CA demodulation test requirements (Rel-17) |
China Telecom |
R4-2205740 |
Draft CR on correction to test applicability reference for CA performance requirements (TS38.101-4, Rel-16) |
Huawei,HiSilicon |
R4-2205741 |
Draft CR on correction to test applicability reference for CA performance requirements (TS38.101-4, Rel-17) |
Huawei,HiSilicon |
R4-2205742 |
Draft CR on update on HST DPS channel model (38.101-4, Rel16) |
Huawei,HiSilicon |
R4-2205743 |
Draft CR on update on HST DPS channel model (38.101-4, Rel17) |
Huawei,HiSilicon |
R4-2205744 |
Draft CR on updating to power saving requirements (TS38.101-4, Rel-16) |
Huawei,HiSilicon |
R4-2205745 |
Draft CR on updating to power saving requirements (TS38.101-4, Rel-17) |
Huawei,HiSilicon |
R4-2206118 |
Draft CR on PDSCH CA requirements |
Qualcomm Incorporated |
R4-2206122 |
Draft CR on PDSCH CA requirements |
Qualcomm Incorporated |
R4-2206124 |
Draft CR on corrections for HST DPS channel model |
Qualcomm Incorporated |
R4-2206128 |
Draft CR on corrections for HST DPS channel model |
Qualcomm Incorporated |
R4-2207258 |
Draft CR on correction to test applicability reference for CA performance requirements (TS38.101-4, Rel-16) |
Huawei,HiSilicon |
R4-2207259 |
Draft CR on corrections for HST DPS channel model |
Qualcomm Incorporated |
R4-2207260 |
Draft CR on updating to power saving requirements (TS38.101-4, Rel-16) |
Huawei,HiSilicon |
5.1.5.4.2 |
CSI requirements |
|
R4-2205746 |
Draft CR on correction to eMIMO FRC (TS38.101-4, Rel-16) |
Huawei,HiSilicon |
R4-2205747 |
Draft CR on correction to eMIMO FRC (TS38.101-4, Rel-17) |
Huawei,HiSilicon |
5.1.5.5 |
NR MIMO OTA test methods (38.827) |
|
R4-2204946 |
Draft CR to TR38.827:DL power for FR1 and FR2 test procedure |
vivo |
R4-2204947 |
Draft CR to TR38.827:power validation procedure correction |
vivo |
R4-2207151 |
Email discussion summary for [102-e][334] NR_MIMO_OTA |
Moderator (CAICT) |
R4-2207305 |
Draft CR to TR38.827:DL power for FR1 and FR2 test procedure |
vivo |
R4-2207424 |
Email discussion summary for [102-e][334] NR_MIMO_OTA |
Moderator (CAICT) |
R4-2207510 |
Big CR for TR 38.827 maintenance (Rel-16, CAT F) |
MCC, vivo |
5.2.2 |
UE RF requirements |
|
R4-2206012 |
DraftCR 36.101 Missing UL CA Configurations |
AT&T |
R4-2206013 |
DraftCR 36.101 Missing UL CA Configurations |
AT&T |
5.2.3 |
RRM requirements |
|
R4-2204885 |
Clarification on asynchronous DAPS handover R16 |
Huawei, Hisilicon |
R4-2204886 |
Clarification on asynchronous DAPS handover R17 |
Huawei, Hisilicon |
R4-2205205 |
Clarification on asynchronous DAPS handover R16 |
Huawei, Hisilicon |
R4-2205206 |
Clarification on asynchronous DAPS handover R17 |
Huawei, Hisilicon |
R4-2205324 |
Correction to DAPS handover test cases in TS36.133 R16 |
Huawei, HiSilicon |
R4-2205325 |
Correction to DAPS handover test cases in TS36.133 R17 |
Huawei, HiSilicon |
R4-2205414 |
TDD UL-DL and DL-UL switching in LTE DAPS handover |
Ericsson |
R4-2205415 |
Correction on the synchronous condition for DAPS handover |
Ericsson |
R4-2205416 |
Correction on the synchronous condition for DAPS handover |
Ericsson |
R4-2206831 |
WF on LTE RRM Maintenance |
Ericsson |
R4-2206834 |
Correction to DAPS handover test cases in TS36.133 R16 |
Huawei, Hisilicon |
R4-2207023 |
Correction to reference point defintion for UE timing in TS 38.133 |
Ericsson, Intel, Huawei, HiSilicon, Qualcomm |
6.1.1 |
UE RF requirements |
|
R4-2206303 |
Email discussion summary for [102-e][103] R17_Maintenance |
Moderator (Ericsson) |
R4-2206403 |
Email discussion summary for [102-e][103] R17_Maintenance |
Moderator (Ericsson) |
6.2.1 |
BS RF requirements |
|
R4-2203583 |
CR to TR 38.921: Update of information about interference management in subclause 6.1.4, 6.1.5, 8.1.2 and 9.2 |
Ericsson |
R4-2204562 |
Updating fOOB and fOBUE for n41 and n90 1-C BS |
CMCC |
R4-2204563 |
CR to TS 38.104 - fOOB and fOBUE for band n41 and n90 for 1-C BS |
CMCC |
R4-2205487 |
Draft maintenance CR to TS38.104 |
ZTE Corporation |
R4-2205488 |
Draft maintenance CR to TS36.141 |
ZTE Corporation |
R4-2207309 |
Draft maintenance CR to TS36.141 |
ZTE Corporation |
R4-2207310 |
CR to TR 38.921: Update of information about interference management in subclause 6.1.4, 6.1.5, 8.1.2 and 9.2 |
Ericsson |
6.2.2 |
UE RF requirements |
|
R4-2203675 |
CR for TS 38.101-3 Rel-17: Corrections on UE co-existence |
Apple |
R4-2203708 |
Draft CR 38.101-3: Rel-17 Correction of bugs in combinations tables |
Apple |
R4-2203993 |
CR to TS 38.307 on NR intra-band CA BW class within FR1 (Rel-17) |
ZTE Corporation |
R4-2204086 |
CR to TS38101-1 Addition of DC configurations |
Huawei, HiSilicon, BT |
R4-2204087 |
CR to TS38101-3 Addition of UL configurations for EN-DC |
Huawei, HiSilicon, BT |
R4-2204140 |
Clarification of A-MPR/NS applicability for inter-band NR-DC |
SoftBank Corp. |
R4-2204313 |
draft CR for n74 related CA co-existence requirements for TS 38.101-1 |
KDDI Corporation |
R4-2204331 |
draft CR for n74 related CA co-existence requirements for TS 38.101-1 |
KDDI, NTT DoCoMo, Softbank |
R4-2204604 |
Extending the deployment scenarios for UE TX switching: completing the RAN4 specification for non-colocation |
Ericsson |
R4-2204605 |
Introduction of TX switching for non-collocated UL CA and EN-DC |
Ericsson |
R4-2205116 |
Draft CR for 38.101-3 Rel-17 to modify the notes and correct the superscripts for inter-band EN-DC configurations |
Xiaomi |
R4-2205180 |
CR for TS 38.101-1 Rel-17: Corrections on UE co-existence |
Apple |
R4-2205293 |
CR for 38.101-1 to correct the REFSENS errors due to the new format(n41 n77 n78) (R17) |
Huawei, HiSilicon |
R4-2206105 |
Clarification of modifiedMPR-Behavior for PC1.5 |
Qualcomm Incorporated |
R4-2206130 |
CR R17 TS38.101-1 on TDD REFSENS and MSDs |
Skyworks Solutions Inc., Apple |
R4-2206354 |
CR for TS 38.101-3 Rel-17: Corrections on UE co-existence |
Apple |
R4-2206355 |
CR to TS38101-1 Addition of DC configurations |
Huawei, HiSilicon, BT |
R4-2206356 |
Clarification of A-MPR/NS applicability for inter-band NR-DC |
SoftBank Corp. |
R4-2206357 |
Draft CR for 38.101-3 Rel-17 to modify the notes and correct the superscripts for inter-band EN-DC configurations |
Xiaomi |
R4-2206358 |
CR for TS 38.101-1 Rel-17: Corrections on UE co-existence |
Apple |
R4-2206585 |
CR 38.101-3: Rel-17 Correction of bugs in combinations tables |
Apple |
6.2.4 |
Demodulation and CSI requirements |
|
R4-2205911 |
Draft CR to TS38.101-4, Correction the misalignment for subsection 5.2.2.2.15 in Rel-16 and Rel-17 |
MediaTek inc. |
7 |
LS response to ITU |
|
R4-2207149 |
Email discussion summary for [102-e][315] LS_Response_ITU-R |
Moderator (Ericsson) |
R4-2207422 |
Email discussion summary for [102-e][315] LS_Response_ITU-R |
Moderator (Ericsson) |
7.1 |
Generic unwanted emission (IMT-2020) |
|
R4-2203621 |
On the LS response to ITU-R on Generic unwanted emission (IMT-2020) |
Ericsson |
R4-2203622 |
Progress report from ITU-R WP5D (7-23 February) on unwanted emissions |
Ericsson |
R4-2207262 |
WF on LS response to ITU-R on Generic unwanted emission (IMT-2020 |
Ericsson, Nokia, Huawei, Qualcomm, ZTE |
8 |
Rel-17 feature list |
|
R4-2203657 |
UE features for enhanced IIoT and URLLC |
Nokia |
R4-2203809 |
Further discussion on R17 feature list |
Apple |
R4-2203851 |
A new Rel-17 per-FR MG capability based on Per BC |
Qualcomm Incorporated |
R4-2204054 |
Inputs to Rel-17 NR UE features for measurement gap enhancement and UE power saving enhancement |
MediaTek inc. |
R4-2204428 |
Discussion on Rel-17 RAN4 UE feature list |
Intel Corporation |
R4-2204479 |
Continue discussion on capability signaling for HPUE NR DC |
MediaTek Inc. |
R4-2204484 |
draft LS to RAN2 for NR CA_DC power class |
MediaTek Inc. |
R4-2204651 |
Update on Rel-17 RAN4 UE feature list for NR |
vivo |
R4-2204687 |
Discussion on Fs_inter for FR2-1 inter-band DL CA based on CBM within same frequency group |
LG Electronics |
R4-2205191 |
On Rel-17 feature list |
Huawei, HiSilicon |
R4-2206051 |
On rel-17 UE features |
Nokia, Nokia Shanghai Bell |
R4-2206098 |
R17 UE feature list proposal |
Qualcomm communications-France |
R4-2206282 |
LS on Rel-17 RAN4 UE feature list for NR |
CMCC |
R4-2206283 |
Rel-17 RAN4 UE feature list for NR |
CMCC |
R4-2206343 |
Email discussion summary for [102-e][143] R17_feature_list |
Moderator (CMCC) |
R4-2206443 |
Email discussion summary for [102-e][143] R17_feature_list |
Moderator (CMCC) |
R4-2206571 |
Rel-17 UE feature list (update) |
CMCC |
R4-2206572 |
LS on Rel-17 RAN4 UE feature list for NR |
CMCC |
9.1 |
Introduction of lower 6GHz NR unlicensed operation for Europe |
|
R4-2206359 |
WF on NSs for n102 |
Apple |
9.1.1 |
General |
|
R4-2203658 |
Overview of the Region 1 countries implementing lower 6GHz unlicensed band |
Apple |
R4-2205559 |
draft TR 38.849 v0.7.0 |
Nokia, Nokia Shanghai Bell |
R4-2206305 |
Email discussion summary for [102-e][105] NR_6GHz_unlic_EU |
Moderator (Nokia) |
R4-2206405 |
Email discussion summary for [102-e][105] NR_6GHz_unlic_EU |
Moderator (Nokia) |
9.1.2 |
Band definition and channel arrangement |
|
R4-2205560 |
On band definition for the lower 6GHz NR unlicensed operation |
Nokia, Nokia Shanghai Bell |
R4-2206360 |
CR to TS 36.104 the introduction of EU unlicensed band n102 |
ZTE |
R4-2206361 |
CR to TS 38.141-2 the introduction of EU unlicensed band n102 |
ZTE |
R4-2206362 |
CR to 37.145-1 - adding band n102 |
Huawei |
R4-2206363 |
CR to 37.145-2 - adding band n102 |
Huawei |
R4-2206581 |
CR to 38.101-2: Addition of a note for per-beam based P-MPR |
Nokia, Nokia Shanghai Bell |
R4-2206592 |
CR to 37.145-1 - adding band n102 |
Huawei |
9.1.3 |
UE RF requirements |
|
R4-2203659 |
CR for introduction of the lower 6GHz unlicensed band |
Apple, Skyworks Solutions Inc., MediaTek Inc. |
R4-2204606 |
Unwanted emissions requirements for lower 6GHz NR unlicensed operation for Europe |
Ericsson |
R4-2204607 |
Unwanted emissions requirements for Band n102 |
Ericsson |
R4-2206364 |
CR for introduction of the lower 6GHz unlicensed band |
Apple, Skyworks Solutions Inc., MediaTek Inc. |
R4-2206365 |
Unwanted emissions requirements for Band n102 |
Ericsson |
R4-2206480 |
WF on feasibility study on max power reduction for PRACH, PUCCH, and full-PRB PUSCH |
Ericsson |
9.1.4 |
BS RF requirements |
|
R4-2205561 |
CR for 38.104 to introduce n102 |
Nokia, Nokia Shanghai Bell |
R4-2205944 |
CR to 37.104 on introduction of n102 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2205946 |
CR to 37.141 on introduction of n102 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2205947 |
CR to 36.141 on introduction of n102 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2205950 |
CR to 38.141-1 on introduction of n102 requirements |
Nokia, Nokia Shanghai Bell |
R4-2206041 |
CR for 37.105 on Introduction of lower 6GHz NR unlicensed operation for Europe |
Ericsson GmbH, Eurolab |
R4-2206366 |
CR for 38.104 to introduce n102 |
Nokia, Nokia Shanghai Bell |
9.1.5 |
Others |
|
R4-2203660 |
TP for TR 38.849 |
Apple |
R4-2206367 |
TP for TR 38.849 |
Apple |
9.2 |
Introduction of operation in full unlicensed band 5925-7125MHz for NR |
|
R4-2206368 |
WF on introduction of the full unlicensed band |
Apple |
9.2.1 |
General |
|
R4-2205562 |
On band definition for 6GHz NR unlicensed operation |
Nokia, Nokia Shanghai Bell |
R4-2206306 |
Email discussion summary for [102-e][106] NR_6GHz_unlic_full |
Moderator (Apple) |
R4-2206406 |
Email discussion summary for [102-e][106] NR_6GHz_unlic_full |
Moderator (Apple) |
9.2.2 |
Regulatory requirements and evaluation for re-using existing NS |
|
R4-2203661 |
Applicability of band n96 |
Apple |
9.2.3 |
UE RF requirements |
|
R4-2203662 |
On the VLP mode for the NR-U operation |
Apple |
R4-2203663 |
CR for introduction of operation in full unlicensed band 5925-7125MHz |
Apple |
R4-2204091 |
Discussion on NR-U MPR and A-MPR for type 1 waveforms |
Skyworks Solutions Inc. |
R4-2204729 |
Draft CR on NR-U A-MPR for PC5 VLP in South Korea |
LG Electronics Inc. |
R4-2204733 |
A-MPR analysis results for NR-U(VLP) considering regulatory parameters in Korea |
LG Electronics Inc. |
R4-2204991 |
Draft CR_NR-U A-MPR for PC5 VLP in South Korea |
LG Electronics Inc. |
R4-2206066 |
A-MPR related to in-band PSD for n96 UE in Korea |
Skyworks Solutions Inc. |
R4-2206369 |
A-MPR analysis results for NR-U(VLP) considering regulatory parameters in Korea |
Main Session |
R4-2206370 |
CR for introduction of operation in full unlicensed band 5925-7125MHz |
Apple |
9.2.5 |
Others |
|
R4-2203664 |
TP for TR 38.849 |
Apple |
R4-2205179 |
Text proposal for TR 38.849 (background results for the existing A-MPR values) |
Apple |
9.3.1 |
General |
|
R4-2203665 |
Initial considerations on requirements for the licensed operation in the upper 6GHz frequency range |
Apple |
R4-2203666 |
Further Reply LS on inclusion of the 6425-7125 MHz frequency band in the 3GPP specification for 5G-NR/IMT-2000 systemss |
Apple |
R4-2203868 |
On RCC recommendation and coexistence in 6GHz licensed band |
Skyworks Solutions Inc. |
R4-2203918 |
General issues for 6GHz licensed band |
CATT |
R4-2204564 |
Discussion about the LS to RCC |
CMCC |
R4-2205059 |
General aspects - n104 |
Ericsson |
R4-2205143 |
Clarification on RCC Recommendation |
Huawei, HiSilicon |
R4-2205144 |
Draft LS on futher clarification on RCC Recommendation 1/21 |
Huawei, HiSilicon |
R4-2205452 |
Discussion on general aspects for licensed 6GHz |
ZTE Corporation |
R4-2206129 |
6GHz licensed band coexistence aspects |
MediaTek (Chengdu) Inc. |
R4-2206307 |
Email discussion summary for [102-e][107] NR_6 GHz_licensed |
Moderator (Huawei) |
R4-2206375 |
Further Reply LS on inclusion of the 6425-7125 MHz frequency band in the 3GPP specification for 5G-NR/IMT-2000 systems |
Apple |
R4-2206407 |
Email discussion summary for [102-e][107] NR_6 GHz_licensed |
Moderator (Huawei) |
9.3.2 |
System parameters |
|
R4-2203919 |
System parameters for 6GHz licensed band |
CATT |
R4-2204565 |
Discussion on system parameters for 6GHz licensed spectrum |
CMCC |
R4-2205120 |
Discussion the remaining issues on system parameters for 6G license band |
Xiaomi |
R4-2205145 |
System parameters for 6GHz NR licensed band |
Huawei, HiSilicon, China Unicom |
R4-2205453 |
Discussion on system parameters for 6425-7125MHz |
ZTE Corporation |
R4-2206102 |
Channel raster and sync raster for the 6 GHz licensed band |
Qualcomm Incorporated |
R4-2206127 |
6GHz licensed band system parameters |
MediaTek (Chengdu) Inc. |
9.3.3 |
UE RF requirements |
|
R4-2203653 |
REFSENS for 6GHz licensed band |
Skyworks Solutions Inc. |
R4-2203654 |
MPR versus ACLR and SEM for 6GHz licensed band |
Skyworks Solutions Inc. |
R4-2203920 |
UE RF requirements for 6GHz licensed band |
CATT |
R4-2204073 |
Discussion on UE RX REFSENS for 6GHz licensed band |
Mediatek India Technology Pvt. |
R4-2204566 |
Discussion on UE requirements for 6GHz licensed spectrum |
CMCC |
R4-2205121 |
Discussion on UE Rx requirements for 6G license band |
Xiaomi |
R4-2205146 |
UE TX RF requirements |
Huawei, HiSilicon |
R4-2205147 |
UE RX RF requirements |
Huawei, HiSilicon, China Unicom |
R4-2205454 |
Discussion on UE RF requirements for 6425-7125MHz |
ZTE Corporation |
R4-2206103 |
UE RF requirements for the 6 GHz licensed band |
Qualcomm Incorporated |
R4-2206104 |
Introduction of NR licensed band 6425 – 7125 MHz |
Qualcomm Incorporated |
R4-2206371 |
WF on general aspects |
Huawei |
R4-2206372 |
WF on system parameters |
Ericsson |
R4-2206373 |
WF on UE RF requirements |
Qualcomm |
R4-2206374 |
WF on BS RF requirements |
Nokia |
R4-2206576 |
Introduction of NR licensed band 6425 – 7125 MHz |
Qualcomm Incorporated |
9.3.4 |
BS RF requirements |
|
R4-2203646 |
Proposals on BS RF requirements for introduction of 6GHz licensed band |
Nokia, Nokia Shanghai Bell |
R4-2203961 |
Remaining issue on RF requirements for BS operating in 6GHz band |
CATT |
R4-2203962 |
Introduction of 6GHz licensed band for 37.105 |
CATT |
R4-2203963 |
Introduction of 6GHz licensed band for 38.174 |
CATT |
R4-2204567 |
Discussion on BS requirements for 6GHz licensed spectrum |
CMCC |
R4-2205060 |
Remaining BS RF open issues and MU - n104 |
Ericsson |
R4-2205062 |
CR to TS 38.141-2 - introduction of band n104 |
Ericsson |
R4-2205063 |
CR to TS 38.176-2 - introduction of band n104 |
Ericsson |
R4-2205148 |
BS RF requirements |
Huawei, HiSilicon, China Unicom |
R4-2205455 |
Discussion on BS RF requirements for 6425-7125MHz |
ZTE Corporation |
R4-2205456 |
draft CR to TS38.104 the introduction of 6425-7125MHz |
ZTE Corporation |
R4-2205457 |
draft CR to TS36.104 the introduction of coexistence requirements of licensed band 6425-7125MHz |
ZTE Corporation |
R4-2205458 |
draft CR to TS36.141 the introduction of coexistence requirements of licensed band 6425-7125MHz |
ZTE Corporation |
R4-2205954 |
draft CR to 37.104 on introduction of n104 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2205955 |
draft CR to 37.141 on introduction of n104 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2206376 |
draft CR to TS38.104 the introduction of 6425-7125MHz |
ZTE Corporation |
9.3.5 |
Others |
|
R4-2203647 |
Draft CR to TR 38.176-1 on introduction of 6GHz licensed band |
Nokia, Nokia Shanghai Bell |
R4-2205061 |
CR to TS 38.133 - introduction of band n104 |
Ericsson |
R4-2206751 |
Email discussion summary for [102-e][208] Spectrum_RRM_NWM |
Moderator (Ericsson) |
R4-2207049 |
Email discussion summary for [102-e][208] Spectrum_RRM_NWM |
Moderator (Ericsson) |
9.4.1 |
General |
|
R4-2204551 |
Version update TR_38.853-0.3.0 |
Union Inter. Chemins de Fer |
R4-2205141 |
TP 900MHz RMR band – conclusion- TR 38.853 |
Union Inter. Chemins de Fer |
R4-2206049 |
Synchronization raster design for n100 |
Nokia, Nokia Shanghai Bell |
R4-2206279 |
TP 1900MHz RMR band – conclusion – TR 38.852 |
Union Inter. Chemins de Fer |
R4-2206280 |
TP 900MHz RMR band – conclusion- TR 38.853 |
Union Inter. Chemins de Fer |
R4-2206281 |
WF on sync raster redesign to enable operation of CBW <5MHz |
Union Inter. Chemins de Fer |
R4-2206308 |
Email discussion summary for [102-e][108] RAIL_900_1900MHz |
Moderator (Union Inter. Chemins de Fer) |
R4-2206377 |
Synchronization raster design for n100 |
Nokia, Nokia Shanghai Bell |
R4-2206408 |
Email discussion summary for [102-e][108] RAIL_900_1900MHz |
Moderator (Union Inter. Chemins de Fer) |
9.4.2 |
UE RF requirements |
|
R4-2204791 |
38.101-1: Introduction of 900 MHz to 5G NR for RMR |
Nokia, UIC |
R4-2206284 |
38.101-1: Introduction of 900 MHz to 5G NR for RMR |
Nokia, UIC |
9.4.3 |
BS RF requirements |
|
R4-2205064 |
CR to TS 38.104 - Tx requirements: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2205065 |
CR to TS 38.141-2: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2205066 |
CR to TS 36.104: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2205067 |
CR to TS 36.141: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2205138 |
TP BS RF conducted requirements for n100 |
Union Inter. Chemins de Fer |
R4-2205943 |
CR to 37.104 on introduction of n100 and n101 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2205945 |
CR to 37.141 on introduction of n100 and n101 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2205948 |
CR to 38.104 on introduction of n100 and n101 (system parameters) |
Nokia, Nokia Shanghai Bell |
R4-2205949 |
CR to 38.141-1 on introduction of n100 and n101 requirements |
Nokia, Nokia Shanghai Bell |
R4-2205994 |
Interferer signal for the BS RF RX blocking requirement for RMR900 |
Huawei, HiSilicon |
R4-2205995 |
draft LS to ETSI TC RT on the interferer signal definition for the RMR900 BS Rx blocking requirement |
Huawei, HiSilicon |
R4-2205996 |
Draft CR to TS 38.104: RX requirements (revision) |
Huawei, HiSilicon |
R4-2207150 |
Email discussion summary for [102-e][314] RAIL_900_1900MHz_BSRF |
Moderator (Huawei) |
R4-2207263 |
CR to TS 38.104 - Tx requirements: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2207264 |
CR to TS 38.141-2: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2207265 |
CR to TS 36.104: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2207266 |
CR to TS 36.141: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2207267 |
TP BS RF conducted requirements for n100 |
Union Inter. Chemins de Fer |
R4-2207268 |
CR to 37.104 on introduction of n100 and n101 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2207269 |
CR to 37.141 on introduction of n100 and n101 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2207270 |
CR to 38.104 on introduction of n100 and n101 (system parameters) |
Nokia, Nokia Shanghai Bell |
R4-2207271 |
CR to 38.141-1 on introduction of n100 and n101 requirements |
Nokia, Nokia Shanghai Bell |
R4-2207273 |
LS to ETSI TC RT on the interferer signal definition for the RMR900 BS Rx blocking requirement |
Huawei |
R4-2207274 |
CR to TS 37.105: RMR implementation |
Huawei, HiSilicon |
R4-2207275 |
CR to TS 37.145-1: RMR implementation |
Huawei |
R4-2207276 |
CR to TS 37.145-2: RMR implementation |
Huawei,HiSilicon |
R4-2207277 |
CR to TS 38.104: RX requirements |
Huawei |
R4-2207423 |
Email discussion summary for [102-e][314] RAIL_900_1900MHz_BSRF |
Moderator (Huawei) |
R4-2207516 |
Big CR to TS 38.104: RMR 1900MHz band n101 introduction |
Nokia |
R4-2207517 |
CR to TS 38.141-1: RMR 1900MHz band n101 introduction |
Nokia, Nokia Shanghai Bell |
R4-2207518 |
CR to TS 38.141-2: RMR 1900MHz band n101 introduction |
Ericsson |
R4-2207519 |
CR to TS 36.104: RMR 1900MHz band n101 introduction |
Ericsson |
R4-2207520 |
CR to TS 36.141: RMR 1900MHz band n101 introduction |
Ericsson |
R4-2207521 |
CR to TS 37.104: RMR 1900MHz band n101 introduction |
Nokia, Nokia Shanghai Bell |
R4-2207522 |
CR to TS 37.141: RMR 1900MHz band n101 introduction |
Nokia, Nokia Shanghai Bell |
R4-2207523 |
CR to TS 37.105: RMR 1900MHz band n101 introduction |
Huawei, HiSilicon |
R4-2207524 |
CR to TS 37.145-1: RMR 1900MHz band n101 introduction |
Huawei, HiSilicon |
R4-2207525 |
CR to TS 37.145-2: RMR 1900MHz band n101 introduction |
Huawei, HiSilicon |
9.5.1 |
General |
|
R4-2204550 |
Version update TR_38.852-0.3.0 |
Union Inter. Chemins de Fer |
R4-2205140 |
TP 1900MHz RMR band – conclusion – TR 38.852 |
Union Inter. Chemins de Fer |
9.5.2 |
UE RF requirements |
|
R4-2204792 |
38.101-1: Introduction of 1900 MHz to 5G NR for RMR |
Nokia, UIC |
9.5.3 |
BS RF requirements |
|
R4-2205139 |
TP BS RF conducted requirements for n101 |
Union Inter. Chemins de Fer |
R4-2207272 |
TP BS RF conducted requirements for n101 |
Union Inter. Chemins de Fer |
9.6 |
Issues arising from basket WIs but not subject to block approval |
|
R4-2206387 |
Discussion on UE RF requirements for DC_20-28_n78 |
VODAFONE Group Plc |
R4-2206388 |
Discussion on UE RF requirements for DC_20-38_n8 |
VODAFONE Group Plc |
R4-2206393 |
WF on missing fall back list for 36.101 and 38.101-1 and -3 |
Apple |
R4-2206394 |
WF on capturing triple beat MSD in 38.101-1 and 38.101-3 |
Apple |
R4-2206395 |
CR to 38.101-3 to add triple beat MSD |
Skyworks, Qualcomm |
R4-2206396 |
WF on NR-U contiguous ULCA MPR |
Skyworks, Qualcomm |
R4-2206397 |
CR to 38.101-1 to add NR-U contiguous UL CA MPR |
Qualcomm, Skyworks |
R4-2206398 |
WF on MSD for DC_(n)3AA |
Huawei |
R4-2206399 |
WF on IMD4 MSD for CA_n28A-n40A-n41A |
ZTE |
R4-2206584 |
WF on CA_n18- n28 and DC_18-n28 low MSD second test point |
Main Session |
9.6.1 |
UE RF requirements |
|
R4-2203538 |
TP to TR 38.717.02-01 for CA_n46-n96 |
Charter Communications, Inc |
R4-2203539 |
TP to TR TR38.717-03-01 for CA_n46-n48-n96 |
Charter Communications, Inc |
R4-2203540 |
TP to TR 38.717.03-02 for CA_n46-n48--n96 |
Charter Communications, Inc |
R4-2203623 |
Discussion on UE RF requirements for DC_8-28_n3 |
VODAFONE Group Plc |
R4-2203624 |
Discussion on UE RF requirements for DC_8-28_n78 |
VODAFONE Group Plc |
R4-2203625 |
Discussion on UE RF requirements for DC_8-32_n78 |
VODAFONE Group Plc |
R4-2203626 |
Discussion on UE RF requirements for DC_20-28_n78 |
VODAFONE Group Plc |
R4-2203627 |
Discussion on UE RF requirements for DC_20-38_n8 |
VODAFONE Group Plc |
R4-2203709 |
Issue of many missing fallbacks in 38.101 specifications |
Apple |
R4-2204090 |
On simultaneous Tx/Rx for constituents of CA_n46-n48-n96 |
Skyworks Solutions Inc. |
R4-2204213 |
CA_n18-n28 and DC_18_n28 LB_LB_MSD |
Qualcomm Incorporated |
R4-2204214 |
CA_n46-n48-n96_Async_MSD |
Qualcomm Incorporated |
R4-2204216 |
DC_2_n25_Fallback_MSD |
Qualcomm Incorporated |
R4-2204217 |
Triple_Beat_MSD_update |
Qualcomm Incorporated |
R4-2204480 |
Discussion on CA_n18_n28 |
MediaTek Inc. |
R4-2204482 |
draft CR to 38101-1-h40 improve note for CA_n18-n28 |
MediaTek Inc. |
R4-2204483 |
draft CR to 38101-1-h40 missing MSD for CA_n5-n77(2A) |
MediaTek Inc. |
R4-2204680 |
Draft Correction CR to R17 TS38.101-1 on MSD for CA_n18-n28 |
Samsung, KDDI, Skyworks Solutions Inc., Qualcomm |
R4-2204681 |
Draft Correction CR to R17 TS38.101-3 on MSD for DC_18_n28 |
Samsung, KDDI, Skyworks Solutions Inc., Qualcomm |
R4-2204736 |
TP for TR 37.717-11-11: Update MSD analysis of DC_(n)3AA |
Huawei Technologies France |
R4-2204806 |
TP for TR 37.717-21-11: Update DC_1A_(n)3AA |
Huawei Technologies France |
R4-2205669 |
TP to TR 38.717.02-01 for CA_n48-n96 and DC_n48-n96 |
Charter Communications, Inc |
R4-2205701 |
TP for TR 37.717-11-11 to include DC_2_n25 |
Ericsson, Bell Mobility |
R4-2205702 |
TP for TR 37.717-21-11 to include DC_2-7_n25 |
Ericsson, Bell Mobility |
R4-2205703 |
TP for TR 37.717-31-11 to include DC_2-7-66_n25 |
Ericsson, Bell Mobility |
R4-2205704 |
TP for TR 37.717-31-11 to include DC_2-7-13_n25 |
Ericsson, Bell Mobility |
R4-2206134 |
CR to R17 TS38.101-1 on MSD for CA_n5-n28 |
Skyworks Solutions Inc. |
R4-2206136 |
Guidelines on MSD due to Cross-band Isolation and Harmonic Interference |
Skyworks Solutions Inc. |
R4-2206140 |
Corrections for CA_n18-n28, DC_18_n18 MSD |
Skyworks Solutions Inc. |
R4-2206141 |
Corrections for CA_n5-n28 MSD |
Skyworks Solutions Inc. |
R4-2206309 |
Email discussion summary for [102-e][109] NR_Baskets_Part_1 |
Moderator (Skyworks) |
R4-2206378 |
Draft Correction CR to R17 TS38.101-1 on MSD for CA_n18-n28 |
Samsung, KDDI, Skyworks Solutions Inc., Qualcomm |
R4-2206379 |
Draft Correction CR to R17 TS38.101-3 on MSD for DC_18_n28 |
Samsung, KDDI, Skyworks Solutions Inc., Qualcomm |
R4-2206380 |
TP to TR 38.717.02-01 for CA_n46-n96 |
Charter Communications, Inc |
R4-2206381 |
TP to TR 38.717.02-01 for CA_n48-n96 and DC_n48-n96 |
Charter Communications, Inc |
R4-2206382 |
TP to TR TR38.717-03-01 for CA_n46-n48-n96 |
Charter Communications, Inc |
R4-2206383 |
TP to TR 38.717.03-02 for CA_n46-n48--n96 |
Charter Communications, Inc |
R4-2206384 |
TP for TR 37.717-11-11 to include DC_2_n25 |
Ericsson, Bell Mobility, Qualcomm |
R4-2206385 |
draft CR to 38101-1-h40 missing MSD for CA_n5-n77(2A) |
MediaTek Inc. |
R4-2206386 |
TP for TR 37.717-11-11: Update MSD analysis of DC_(n)3AA |
Huawei Technologies France |
R4-2206389 |
TP for TR 37.717-21-11 for DC_8-28_n3 |
VODAFONE Group Plc |
R4-2206390 |
TP for TR 37.717-21-11 for DC_8-28_n78 |
VODAFONE Group Plc |
R4-2206391 |
TP for TR 37.717-21-11 for DC_8-32_n78 |
VODAFONE Group Plc |
R4-2206392 |
TP for TR 37.717-21-11 for DC_20-28_n78 |
VODAFONE Group Plc |
R4-2206409 |
Email discussion summary for [102-e][109] NR_Baskets_Part_1 |
Moderator (Skyworks) |
R4-2206485 |
draft CR to 38101-1-h40 missing MSD for CA_n5-n77(2A) |
NTT DOCOMO INC. |
9.6.2 |
NR-U intra-band contiguous UL CA |
|
R4-2206076 |
Proposals for NR-U Intraband Contiguous UL-CA requirements |
Qualcomm Incorporated |
R4-2206138 |
MPR proposal for NR-U UL-CA |
Skyworks Solutions Inc. |
9.6.3 |
Low MSD for CA and DC |
|
R4-2204088 |
On low MSD for CA and DC |
Huawei, HiSilicon |
9.7.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205674 |
Revised WID NR Intra-band Rel-17 |
Ericsson |
R4-2205678 |
Big CR 38.101-1 new combinations Rel-17 NR Intra-band |
Ericsson |
R4-2205679 |
Big CR 38.101-2 new combinations Rel-17 NR Intra-band |
Ericsson |
R4-2205684 |
TR 38.717-01-01 v0.8.0 Rel-17 NR Intra-band |
Ericsson |
R4-2206310 |
Email discussion summary for [102-e][110] NR_Baskets_Part_2 |
Moderator (Nokia) |
9.7.2 |
UE RF requirements for FR1 |
|
R4-2205176 |
Draft CR for TS 38.101-1: Correction for intra-band non-contiguous CA operating bands table |
Apple |
R4-2205253 |
Draft CR for 38.101-1 To configuration CA_n3(2A)_BCS1 |
Huawei, HiSilicon |
R4-2205254 |
TP for TR 38.717-01-01 CA_n3B_BCS0 |
Huawei, HiSilicon |
R4-2205255 |
TP for TR 38.717-01-01 CA_n38B_BCS0 |
Huawei, HiSilicon |
R4-2206270 |
TP for TR 38.717-01-01 CA_n3B_BCS0 |
Huawei, HiSilicon |
R4-2206271 |
TP for TR 38.717-01-01 CA_n38B_BCS0 |
Huawei, HiSilicon |
9.8 |
NR inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1, 2) |
|
R4-2205218 |
TR 38.717-02-01 v0.8.0 |
ZTE Wistron Telecom AB |
R4-2206628 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 |
ZTE |
9.8.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204769 |
Revised WID on Rel-17 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
R4-2204770 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-1 |
ZTE Corporation |
R4-2204771 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-3 |
ZTE Corporation |
R4-2206311 |
Email discussion summary for [102-e][111] NR_Baskets_Part_3 |
Moderator (Nokia) |
9.8.2 |
NR inter band CA requirements without any FR2 band(s) |
|
R4-2204755 |
Draft CR to TS38.101-1[R17] CA_n3A-n8A_BCS1 |
ZTE Corporation |
R4-2204756 |
Draft CR to TS38.101-1[R17] CA_n3A-n79A_BCS1 |
ZTE Corporation |
R4-2204757 |
Draft CR for TS 38.101-2 Add a note for BCS in 2DL NR CA table |
ZTE Corporation |
R4-2204793 |
CR TS38.101-1 introduction of CA_n29-n71 |
Dish Network, Nokia, Qualcomm Inc., Skyworks Solutions Inc. |
R4-2205256 |
TP for TR 38.717-02-01 CA_n28A-n38A |
Huawei, HiSilicon |
R4-2205257 |
TP for TR 38.717-02-01 CA_n1A-n38A / CA_n1(2A)-n38A |
Huawei, HiSilicon |
R4-2205258 |
Draft CR for 38.101-1 to add configuration CA_n1A-n28A_BCS1 |
Huawei, HiSilicon |
R4-2205259 |
Draft CR for 38.101-1 to add configuration CA_n3A-n28A_BCS2 |
Huawei, HiSilicon |
R4-2205260 |
Draft CR for 38.101-1 to add configuration CA_n1A-n3B_BCS0/CA_n1A-n3(2A)_BCS2/CA_n1(2A)-n3(2A)/CA_n1(2A)-n3B |
Huawei, HiSilicon |
R4-2205261 |
Draft CR for 38.101-1 to add configuration CA_n1(2A)-n79A and CA_n1(2A)-n79C |
Huawei, HiSilicon |
R4-2205262 |
Draft CR for 38.101-1 to add configuration CA_n3B-n7A / CA_n3(2A)-n7A_BCS1 |
Huawei, HiSilicon |
R4-2205263 |
Draft CR for 38.101-1 to add configuration CA_n3B-n38A / CA_n3(2A)-n38A |
Huawei, HiSilicon |
R4-2205264 |
Draft CR for 38.101-1 to add configuration CA_n3B-n79A / CA_n3(2A)-n79A |
Huawei, HiSilicon |
R4-2205265 |
Draft CR for 38.101-1 to add configuration CA_n3B-n78A / CA_n3(2A)-n78A |
Huawei, HiSilicon |
R4-2205266 |
TP for TR 38.717-02-01 CA_n38A-n79A / CA_n38A-n79C |
Huawei, HiSilicon |
R4-2205267 |
TP for TR 38.717-02-01 CA_n7A-n79A / CA_n7A-n79C |
Huawei, HiSilicon |
R4-2205268 |
Draft CR for 38.101-1 to add configuration CA_n78A-n79C |
Huawei, HiSilicon |
R4-2205564 |
draftCR to add BCS for CA_n40A-n78A to 38.101-1 |
Nokia |
R4-2205566 |
draftCR to add DC_n1A-n28A to 38.101-1 |
Nokia, BT |
R4-2205711 |
draft CR 38.101-1 to make editorial corrections in 2 bands NR CA configuration tables. |
Ericsson |
R4-2206244 |
Draft CR for TS 38.101-2 Add a note for BCS in 2DL NR CA table |
ZTE Corporation |
R4-2206245 |
TP for TR 38.717-02-01 CA_n1A-n38A / CA_n1(2A)-n38A |
Huawei, HiSilicon |
R4-2206246 |
Draft CR for 38.101-1 to add configuration CA_n1A-n28A_BCS1 |
Huawei, HiSilicon |
R4-2206247 |
TP for TR 38.717-02-01 CA_n38A-n79A / CA_n38A-n79C |
Huawei, HiSilicon |
R4-2206248 |
TP for TR 38.717-02-01 CA_n7A-n79A / CA_n7A-n79C |
Huawei, HiSilicon |
R4-2206249 |
draftCR to add BCS for CA_n40A-n78A to 38.101-1 |
Nokia |
9.8.3 |
NR inter band CA requirements with at least one FR2 band |
|
R4-2205712 |
draft CR 38.101-3 to make editorial corrections in 2 bands NR CA configuration tables. |
Ericsson |
9.9.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2203965 |
TR 38.717-03-01 on Rel-17 NR inter-band Carrier Aggregation (CA) for 3 Down Link (DL) / 1 Up Link (UL) v.0.7.0 |
CATT |
R4-2203966 |
Revised WID on Rel-17 NR inter-band CA of 3DL bands and 1UL band |
CATT |
R4-2203967 |
CR on Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-1 |
CATT |
R4-2203968 |
CR on Introducing NR inter-band CA for 3DL Bands and 1UL band for 38.101-3 |
CATT |
9.9.2 |
UE RF requirements |
|
R4-2204138 |
Draft CR for 38.101-3: support of DL n77(3A) in NR-CA of CA_n28A-n77-n257A/G/H/I |
SoftBank Corp. |
R4-2204753 |
TP for TR38.717-03-01: CA_n28A-n40A-n41A |
ZTE Corporation |
R4-2205171 |
DraftCR for 38.101-1: additional combinations for CA_n7-n25-n66 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2205172 |
DraftCR for 38.101-1: CA_n25(2A)-n38A-n66(2A) |
Huawei, HiSilicon, Bell Mobility, Telus |
9.10.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205676 |
Revised WID 4 DL/1UL NR CA Rel-17 |
Ericsson |
R4-2205681 |
Big CR 38.101-1 new combinations NR CA Inter-band 4DL/1UL |
Ericsson |
R4-2205682 |
Big CR 38.101-3 new combinations NR CA Inter-band 4DL/1UL |
Ericsson |
R4-2205686 |
TR 38.717-04-01 v0.8.0 Rel-17 NR CA Inter-band 4DL/1UL |
Ericsson |
9.10.2 |
UE RF requirements |
|
R4-2204758 |
Draft CR for TS 38.101-3 Add a note for BCS in 4DL NR CA table |
ZTE Corporation |
R4-2205168 |
TP for TR 38.717-04-01: CA_n25-n38-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2205169 |
TP for TR 38.717-04-01: CA_n25-n66-n71-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2205170 |
DraftCR for 38.101-1: additional combinations for CA_n7-n25-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2205713 |
draft CR 38.101-1 to add back 5 MHz for n1A in CA_n1A-n3A-n5A-n78A |
Ericsson |
9.11 |
NR Inter-band Carrier Aggregation/Dual connectivity for 3 bands DL with 2 bands UL |
|
R4-2205219 |
TR 38.717-03-02 v0.8.0 |
ZTE Wistron Telecom AB |
9.11.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2203984 |
Revised WID on Rel-17 NR Inter-band Carrier AggregationDual Connectivity for 3 bands DL with 2 bands UL, ZTE Corporation |
ZTE Corporation |
R4-2203985 |
Big CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into TS 38.101-1 |
ZTE Corporation |
R4-2203986 |
Big CR to reflect the completed NR inter band CA DC combinations for 3 bands DL with 2 bands UL into TS 38.101-3 |
ZTE Corporation |
9.11.2 |
UE RF requirements |
|
R4-2204130 |
Draft CR for 38.101-1: support of DL n77(2A) in 2UL CA of CA_n1A-n28A-n77 |
SoftBank Corp. |
R4-2204131 |
Draft CR for 38.101-1: support of Inter-band NR-DC of DC_n1A-n3A-n28A, DC_n1A-n3A-n41A, DC_n1A-n28A-n41A, DC_n1A-n28A-n77A, DC_n1A-n28A-n79A and DC_n1A-n41A-n77A |
SoftBank Corp. |
R4-2204754 |
TP for TR38.717-03-02: CA_n28A-n40A-n41A |
ZTE Corporation |
R4-2205563 |
draftCR to add CA_n40-n77-n257 to 38.101-3 |
Nokia, NBN |
R4-2205565 |
draftCR to add BCS for CA_n1A-n40A-n78A to 38.101-1 |
Nokia |
R4-2205567 |
draftCR to add DC_n1A-n28A-78A to 38.101-1 |
Nokia, BT |
R4-2205568 |
draftCR to add DC_n3A-n28A-78A to 38.101-1 |
Nokia, BT |
R4-2205693 |
TP for TR 38.717-03-02 to include CA_n41-n66-n70 |
Ericsson |
R4-2205694 |
TP for TR 38.717-03-02 to include CA_n66-n70-n78 |
Ericsson |
R4-2205698 |
draft CR 38.101-1 to add UL configurations for CA_n3-n7-n28 and CA_n3-n28-n78 |
Ericsson, BT plc |
R4-2205699 |
draft CR 38.101-1 to add configurations for CA_n3-n7-n78 |
Ericsson, BT plc |
R4-2206250 |
TP for TR38.717-03-02: CA_n28A-n40A-n41A |
ZTE Corporation |
R4-2206251 |
TP for TR 38.717-03-02 to include CA_n41-n66-n70 |
Ericsson |
9.12.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204670 |
Big CR on introduction of completed NR CA/DC combs with 4DL/2UL within FR1 |
Samsung |
R4-2204671 |
Big CR on introduction of completed NR CA/DC combs with 4DL/2UL including FR2 |
Samsung |
R4-2204672 |
Revised WID on NR CA/DC with 4DL/2UL |
Samsung |
R4-2204677 |
TR 38.717-04-02 update version 0.8.0 |
Samsung |
R4-2204699 |
TR 38.717-04-02 update version 0.8.0 |
Samsung |
9.12.2 |
UE RF requirements |
|
R4-2203816 |
TP for TR TR 38.717-04-02: CA_n2-n5-n48-n66 |
Verizon. Samsung |
R4-2203817 |
TP for TR TR 38.717-04-02: CA_n5-n48-n66-n77 |
Verizon. Samsung |
R4-2203825 |
TP for TR 38.717-04-02 to include CA_n2-n5-n66-n77 |
Verizon, Samsung |
R4-2203826 |
TP for TR TR 38.717-04-02: CA_n2-n5-n48-n77 |
Verizon, Samsung |
R4-2203827 |
TP for TR TR 38.717-04-02: CA_n2-n48-n66-n77 |
Verizon, Samsung |
R4-2204094 |
TP for TR 38.717-04-02: CA_n1-n3-n28-n77 |
SoftBank Corp. |
R4-2204095 |
TP for TR 38.717-04-02: CA_n1-n3-n28-n79 |
SoftBank Corp. |
R4-2204096 |
TP for TR 38.717-04-02: CA_n1-n3-n28-n257 |
SoftBank Corp. |
R4-2204097 |
TP for TR 38.717-04-02: CA_n1-n3-n77-n79 |
SoftBank Corp. |
R4-2204099 |
TP for TR 38.717-04-02: CA_n1-n3-n79-n257 |
SoftBank Corp. |
R4-2204100 |
TP for TR 38.717-04-02: CA_n1-n28-n77-n79 |
SoftBank Corp. |
R4-2204102 |
TP for TR 38.717-04-02: CA_n1-n28-n77-n257 |
SoftBank Corp. |
R4-2204103 |
TP for TR 38.717-04-02: CA_n1-n28-n79-n257 |
SoftBank Corp. |
R4-2204104 |
TP for TR 38.717-04-02: CA_n3-n28-n41-n257 |
SoftBank Corp. |
R4-2204105 |
TP for TR 38.717-04-02: CA_n3-n41-n77-n257 |
SoftBank Corp. |
R4-2204106 |
TP for TR 38.717-04-02: CA_n28-n41-n77-n257 |
SoftBank Corp. |
R4-2204135 |
Draft CR for 38.101-3: support of Inter-band NR-DC of DC_n3A-n77A/(2A)-n79A-n257A/G/H/I |
SoftBank Corp. |
R4-2204682 |
Draft CR for 38.101-1 to introduce new configurations to CA_n7-n25-n66-n78 |
Samsung, Telus, Bell Mobility |
R4-2204683 |
TP for TR 38.717-04-02 CA_n2-n5-n66-n77 |
Samsung, Telus, Bell Mobility |
R4-2204684 |
TP for TR 38.717-04-02 CA_n5-n30-n66-n77 |
Samsung, Telus, Bell Mobility |
R4-2204685 |
TP for TR 38.717-04-02 CA_n25-n38-n66-n78 |
Samsung, Telus, Bell Mobility |
R4-2204686 |
TP for TR 38.717-04-02 CA_n25-n66-n71-n78 |
Samsung, Telus, Bell Mobility |
R4-2205569 |
draftCR to add n78(2A) to excisting combinations in 38.101-1 |
Nokia, BT |
R4-2205571 |
draftCR to add DC_12A_n77C to 38.101-3 |
Nokia, US Cellular |
R4-2205692 |
TP for TR 38.717-04-02 to include CA_n41-n66-n70-n78 |
Ericsson |
R4-2205700 |
draft CR 38.101-1 to add new 4DL2UL configurations |
Ericsson, BT plc, Telstra |
R4-2206252 |
Draft CR for 38.101-3: support of Inter-band NR-DC of DC_n3A-n77A/(2A)-n79A-n257A/G/H/I |
SoftBank Corp. |
R4-2206253 |
draftCR to add n78(2A) to excisting combinations in 38.101-1 |
Nokia, BT |
R4-2206254 |
draftCR to add DC_12A_n77C to 38.101-3 |
Nokia, US Cellular |
9.13.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205239 |
Revised WID on NR inter-band CA for 5 bands DL with x bands UL (x=1, 2) |
Huawei, HiSilicon |
R4-2205240 |
TR 38.717-05-01 v0.5.0 |
Huawei, HiSilicon |
R4-2205241 |
CR on Introduction of completed 5 bands inter-band CA into TS 38.101-1 |
Huawei, HiSilicon |
R4-2205242 |
CR on Introduction of completed 5 bands inter-band CA into TS 38.101-3 |
Huawei, HiSilicon |
9.13.2 |
UE RF requirements |
|
R4-2203815 |
TP to TR 38.717-05-01: CA_n2-n5-n48-n66-n77 |
Verizon, Samsung |
R4-2203828 |
TP for TR 38.717-05-01: CA_n2-n5-n48-n66-n77 |
Verizon, Samsung |
R4-2204134 |
TP update for TR 38.717-05-01: CA_n3-28-n77-n79-n257 |
SoftBank Corp. |
R4-2204759 |
Draft CR for TS 38.101-3 Add notes for BCS in 5DL NR CA table |
ZTE Corporation |
R4-2205570 |
draftCR to add CA_n1A-n3A-n7A-n28A-n78(2A) to 38.101-1 |
Nokia, BT |
R4-2206255 |
TP to TR 38.717-05-01: CA_n2-n5-n48-n66-n77 |
Verizon, Samsung |
R4-2206256 |
Draft CR for TS 38.101-3 Add notes for BCS in 5DL NR CA table |
ZTE Corporation |
R4-2206257 |
draftCR to add CA_n1A-n3A-n7A-n28A-n78(2A) to 38.101-1 |
Nokia, BT |
9.14.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204043 |
Big CR for Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2204044 |
Revised WID for Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2204045 |
TR 37.717-11-11 v1.1.0 Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2204047 |
TP for TR 37.717-11-11: general part update |
CHTTL |
9.14.2 |
EN-DC requirements without FR2 band |
|
R4-2205695 |
TP for TR 37.717-11-11 to include DC_20_n67 |
Ericsson, BT plc |
9.15.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205165 |
TR 37.717-21-11 V0.8.0 for DC of 2 LTE band and 1 NR band |
Huawei, HiSilicon |
R4-2205166 |
Revised WID: Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
R4-2205167 |
CR on introduction of completed EN-DC of 2 bands LTE and 1 band NR from RAN4#101bis-e and RAN4#102-e into TS 38.101-3 |
Huawei, HiSilicon |
9.15.2 |
EN-DC requirements without FR2 band |
|
R4-2203628 |
TP for TR 37.717-21-11: DC_8-32_n3 |
VODAFONE Group Plc |
R4-2203629 |
TP for TR 37.717-21-11: DC_8-38_n1 |
VODAFONE Group Plc |
R4-2203630 |
TP for TR 37.717-21-11: DC_28-38_n1 |
VODAFONE Group Plc |
R4-2204554 |
TP for TR 37.717-21-11: EN-DC_8-11_n1 |
SoftBank Corp., LG Electronics |
R4-2205247 |
Updated TP for TR 37.717-21-11: add MSD due to harmonic interference between band n28 and 32 |
Huawei, HiSilicon |
R4-2205709 |
draft CR to remove DC_48A_n77A as possible UL |
Ericsson |
R4-2205710 |
draft CR 38.101-3 to correct DC_20A-38A_n1 in delta TibRib tables |
Ericsson |
R4-2206261 |
TP for TR 37.717-21-11: DC_28-38_n1 |
VODAFONE Group Plc |
R4-2206269 |
Updated TP for TR 37.717-21-11: add MSD due to harmonic interference between band n28 and 32 |
Huawei, HiSilicon |
9.16.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205675 |
Revised WID LTE 3DL and one NR band Rel-17 |
Ericsson |
R4-2205680 |
Big CR 38.101-3 new combinations LTE 3DL and one NR band |
Ericsson |
R4-2205685 |
TR 37.717-31-11 v0.8.0 Rel-17 DC combinations LTE 3DL and one NR band |
Ericsson |
9.16.2 |
EN-DC requirements without FR2 band |
|
R4-2203632 |
TP for TR 37.717-31-11: DC_1-8-20_n3 |
VODAFONE Group Plc |
R4-2203633 |
TP for TR 37.717-31-11: DC_1-8-28_n3 |
VODAFONE Group Plc |
R4-2203634 |
TP for TR 37.717-31-11: DC_1-8-28_n78 |
VODAFONE Group Plc |
R4-2203635 |
TP for TR 37.717-31-11: DC_1-8-32_n3 |
VODAFONE Group Plc |
R4-2204098 |
TP for TR 37.717-31-11: DC_1-8-32_n78 |
VODAFONE Group Plc |
R4-2204101 |
TP for TR 37.717-31-11: DC_1-20-28_n78 |
VODAFONE Group Plc |
R4-2204107 |
TP for TR 37.717-31-11: DC_1-20-38_n8 |
VODAFONE Group Plc |
R4-2204110 |
TP for TR 37.717-31-11: DC_3-8-28_n78 |
VODAFONE Group Plc |
R4-2204112 |
TP for TR 37.717-31-11: EN-DC_1-8-11_n79 |
SoftBank Corp. |
R4-2204113 |
TP for TR 37.717-31-11: DC_3-8-32_n1 |
VODAFONE Group Plc |
R4-2204116 |
TP for TR 37.717-31-11: DC_3-8-32_n78 |
VODAFONE Group Plc |
R4-2204119 |
TP for TR 37.717-31-11: DC_3-20-28_n78 |
VODAFONE Group Plc |
R4-2204122 |
TP for TR 37.717-31-11: DC_7-8-32_n78 |
VODAFONE Group Plc |
R4-2204125 |
TP for TR 37.717-31-11: DC_7-8-38_n1 |
VODAFONE Group Plc |
R4-2204126 |
TP for TR 37.717-31-11: DC_7-20-38_n8 |
VODAFONE Group Plc |
R4-2204127 |
TP for TR 37.717-31-11: DC_7-28-38_n1 |
VODAFONE Group Plc |
R4-2204128 |
TP for TR 37.717-31-11: DC_8-20-28_n78 |
VODAFONE Group Plc |
R4-2204129 |
TP for TR 37.717-31-11: DC_8-20-38_n1 |
VODAFONE Group Plc |
R4-2204136 |
Draft CR for 38.101-3: support of DL n77(3A) in Inter-band 3B LTE EN-DC of DC_1/3/8/11-n77 |
SoftBank Corp. |
R4-2204139 |
TP for TR 37.717-31-11: DC_8-32-38_n1 |
VODAFONE Group Plc |
R4-2204141 |
TP for TR 37.717-31-11: DC_20-28-38_n1 |
VODAFONE Group Plc |
R4-2204142 |
TP for TR 37.717-31-11: DC_28-32-38_n1 |
VODAFONE Group Plc |
R4-2205248 |
Draft CR for 38.101-3 To add configuration DC_1A-3C-32A_n78A |
Huawei, HiSilicon |
R4-2205249 |
Draft CR for 38.101-3 To correct the configuration DC_3C-7A-28A_n1A |
Huawei, HiSilicon, DT |
R4-2205251 |
Updated TP for TR 37.717-31-11 DC_3C-7A-32A_n78A |
Huawei, HiSilicon |
R4-2206262 |
Draft CR for 38.101-3: support of DL n77(3A) in Inter-band 3B LTE EN-DC of DC_1/3/8/11-n77 |
SoftBank Corp. |
9.17.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205547 |
Revised Rel-17 WID on DC of 4 bands LTE inter-band CA (4DL1UL) and 1 NR band (1DL1UL) |
Nokia, Nokia Shanghai Bell |
R4-2205548 |
draft TR 37.717-41-11-080 |
Nokia, Nokia Shanghai Bell |
R4-2205549 |
draft TR 37.717-41-11-090 |
Nokia, Nokia Shanghai Bell |
R4-2205550 |
draftCR to introduce new combinations of LTE 4band + NR 1band for TS 38.101-3 |
Nokia, Nokia Shanghai Bell |
R4-2205551 |
Big CR to introduce new combinations of LTE 4band + NR 1band for TS 38.101-3 |
Nokia, Nokia Shanghai Bell |
9.17.2 |
EN-DC requirements without FR2 band |
|
R4-2203998 |
Draft CR for TS 38.101-3 to add new configuration DC_1A-3A-20A-38A_n78(2A) |
ZTE Corporation |
R4-2204594 |
TP for TR 37.717-41-11: DC_1-3-7-32_n78 |
VODAFONE Group Plc |
R4-2204625 |
TP for TR 37.717-41-11: DC_1-3-8-20_n78 |
VODAFONE Group Plc |
R4-2204626 |
TP for TR 37.717-41-11: DC_1-3-8-28_n78 |
VODAFONE Group Plc |
R4-2204627 |
TP for TR 37.717-41-11: DC_1-3-8-32_n78 |
VODAFONE Group Plc |
R4-2204628 |
TP for TR 37.717-41-11: DC_1-3-20-28_n78 |
VODAFONE Group Plc |
R4-2204630 |
TP for TR 37.717-41-11: DC_1-3-20-32_n78 |
VODAFONE Group Plc |
R4-2204658 |
TP for TR 37.717-41-11: DC_1-7-8-32_n78 |
VODAFONE Group Plc |
R4-2204659 |
TP for TR 37.717-41-11: DC_1-7-20-38_n8 |
VODAFONE Group Plc |
R4-2204660 |
TP for TR 37.717-41-11: DC_1-8-20-28_n78 |
VODAFONE Group Plc |
R4-2204661 |
TP for TR 37.717-41-11: DC_3-7-8-32_n1 |
VODAFONE Group Plc |
R4-2204662 |
TP for TR 37.717-41-11: DC_3-7-8-32_n78 |
VODAFONE Group Plc |
R4-2204663 |
TP for TR 37.717-41-11: DC_3-8-20-28_n78 |
VODAFONE Group Plc |
R4-2204664 |
TP for TR 37.717-41-11: DC_7-8-20-38_n1 |
VODAFONE Group Plc |
R4-2204665 |
TP for TR 37.717-41-11: DC_7-8-32-38_n1 |
VODAFONE Group Plc |
R4-2204666 |
TP for TR 37.717-41-11: DC_7-20-28-38_n1 |
VODAFONE Group Plc |
R4-2204667 |
TP for TR 37.717-41-11: DC_7-28-32-38_n1 |
VODAFONE Group Plc |
R4-2204668 |
TP for TR 37.717-41-11: DC_8-20-32-38_n1 |
VODAFONE Group Plc |
R4-2204669 |
TP for TR 37.717-41-11: DC_20-28-32-38_n1 |
VODAFONE Group Plc |
R4-2204750 |
TP for TR 37.717-41-11: DC_1A-7A-20A-38A_n78A |
ZTE Corporation |
R4-2205252 |
TP for TR 37.717-41-11 DC_1A-3A-7A-32A_n78A and DC_1A-3C-7A-32A_n78A |
Huawei, HiSilicon |
9.18.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204673 |
Big CR introduction completed band combinations for Dual Connectivity (DC) of 5 bands LTE inter-band CA (5DL/1UL) and 1 NR band (1DL/1UL) |
Samsung |
R4-2204674 |
Revised WID on Dual Connectivity (DC) of 5 bands LTE inter-band CA (5DL/1UL) and 1 NR band (1DL/1UL) |
Samsung |
R4-2204678 |
TR 37.717-51-11 update version 0.3.0 |
Samsung |
R4-2204700 |
TR 37.717-51-11 update version 0.3.0 |
Samsung |
9.18.2 |
UE RF requirements |
|
R4-2204689 |
TP for TR 37.717-51-11: DC_1-3-7-8-32_n78 |
VODAFONE Group Plc |
R4-2204690 |
TP for TR 37.717-51-11: DC_1-3-7-20-32_n78 |
VODAFONE Group Plc |
R4-2204691 |
TP for TR 37.717-51-11: DC_1-3-8-20-28_n78 |
VODAFONE Group Plc |
R4-2204692 |
TP for TR 37.717-51-11: DC_7-8-20-32-38_n1 |
VODAFONE Group Plc |
R4-2204693 |
TP for TR 37.717-51-11: DC_7-20-28-32-38_n1 |
VODAFONE Group Plc |
R4-2206263 |
TP for TR 37.717-51-11: DC_1-3-7-8-32_n78 |
VODAFONE Group Plc |
R4-2206264 |
TP for TR 37.717-51-11: DC_1-3-7-20-32_n78 |
VODAFONE Group Plc |
R4-2206265 |
TP for TR 37.717-51-11: DC_1-3-8-20-28_n78 |
VODAFONE Group Plc |
R4-2206266 |
TP for TR 37.717-51-11: DC_7-8-20-32-38_n1 |
VODAFONE Group Plc |
R4-2206267 |
TP for TR 37.717-51-11: DC_7-20-28-32-38_n1 |
VODAFONE Group Plc |
9.19.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204495 |
TR 37.717-11-21 v1.0.0 TR update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics France |
R4-2204510 |
Revised WID on LTE (xDL/UL x=1.2,3,4) with NR 2 bands (2DL/1UL) DC in Rel-17 |
LG Electronics France |
R4-2204513 |
Introduction CR on new NR DC LTE(xDL/1UL)+ NR(2DL/1UL) band combinations in Rel-17 |
LG Electronics France |
R4-2206645 |
TR 37.717-11-21 v1.0.0 TR update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics France |
9.19.2 |
EN-DC requirements including NR inter CA without FR2 band |
|
R4-2204006 |
TP for TR 37.717-11-21: DC_1A-7A_n3A-n38A |
ZTE Corporation |
R4-2204007 |
TP for TR 37.717-11-21: DC_1A-7A-20A_n3A-n38A |
ZTE Corporation |
R4-2204008 |
TP for TR 37.717-11-21: DC_7A-20A_n3A-n38A |
ZTE Corporation |
R4-2204108 |
TP for TR 37.717-11-21: EN-DC_1-3-8_n77-n79 |
SoftBank Corp. |
R4-2204114 |
TP for TR 37.717-11-21: EN-DC_1-11_n3-n79 |
SoftBank Corp. |
R4-2204115 |
TP for TR 37.717-11-21: EN-DC_1-11_n77-n79 |
SoftBank Corp. |
R4-2204120 |
TP for TR 37.717-11-21: EN-DC_8-11_n3-n79 |
SoftBank Corp. |
R4-2204121 |
TP for TR 37.717-11-21: EN-DC_8-11_n77-n79 |
SoftBank Corp. |
R4-2204123 |
TP for TR 37.717-11-21: EN-DC_8-41_n1-n77 |
SoftBank Corp. |
R4-2204124 |
TP for TR 37.717-11-21: EN-DC_8-42_n1-n3 |
SoftBank Corp. |
R4-2204132 |
TP for TR 37.717-11-21: EN-DC_11_n1-n77 |
SoftBank Corp. |
R4-2204151 |
TP on summary of self-interference analysis for new NR DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics France |
R4-2204745 |
TP for TR 37.717-11-21: DC_7A-20A-38A_n3A-n78A |
ZTE Corporation |
R4-2204746 |
TP for TR 37.717-11-21: DC_1A-7A-38A_n3A-n78A |
ZTE Corporation |
R4-2204747 |
TP for TR 37.717-11-21: DC_1A-7A-20A_n3A-n78A |
ZTE Corporation |
R4-2204748 |
TP for TR 37.717-11-21: DC_1A-7A-20A-38A_n3A-n78A |
ZTE Corporation |
R4-2204751 |
TP for 37.717-11-21: DC_3_n41-n258 |
ZTE Corporation |
R4-2204752 |
TP for 37.717-11-21: DC_8_n41-n258 |
ZTE Corporation |
R4-2205250 |
Draft CR for 38.101-3 To remove the duplicated configurations in the spec |
Huawei, HiSilicon, DT |
R4-2205688 |
TP for TR 37.717-11-21 to include DC_5_n1-n78 |
Ericsson, Airtel |
R4-2205689 |
TP for TR 37.717-11-21 to include DC_5_n3-n78 |
Ericsson, Airtel |
R4-2205690 |
TP for TR 37.717-11-21 to include DC_8_n3-n78 |
Ericsson, Airtel |
R4-2205696 |
TP for TR 37.717-11-21 to include DC_20_n1-n67 |
Ericsson, BT plc |
R4-2205697 |
TP for TR 37.717-11-21 to include DC_20_n3-n67 |
Ericsson, BT plc |
R4-2206258 |
TP for 37.717-11-21: DC_3_n41-n258 |
ZTE Corporation |
R4-2206259 |
TP for 37.717-11-21: DC_8_n41-n258 |
ZTE Corporation |
9.19.3 |
EN-DC requirements including NR inter CA with FR2 band |
|
R4-2203994 |
CR to TS 38.101-3 on corrections to EN-DC configuration DC_5-7-7_n78-n257 |
ZTE Corporation |
R4-2204062 |
draft CR for DC_7-8_n78-n257, DC_3-3-8_n78-n257, DC_7-7-8_n78-n257, DC_3-7-8_n78-n257, DC_3-3-7-8_n78-n257, DC_3-7-7-8_n78-n257, DC_3-3-7-7-8_n78-n257 with n257A up to n257M |
CHTTL |
R4-2204063 |
draft CR for DC_8_n1-n257, DC_3-8_n1-n257, DC_3-3-8_n1-n257, DC_7-8_n1-n257, DC_7-7-8_n1-n257, DC_3-7-8_n1-n257, DC_3-3-7-8_n1-n257, DC_3-7-7-8_n1-n257, DC_3-3-7-7-8_n1-n257 |
CHTTL |
R4-2206260 |
Draft CR to TS 38.101-3 on corrections to EN-DC configuration DC_5-7-7_n78-n257 |
ZTE Corporation |
9.20.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204772 |
Revised WID on Rel-17 Dual Connectivity (DC) x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA |
ZTE Corporation |
R4-2204773 |
Big CR to reflect the completed ENDC combinations for 3 bands DL with 3 bands UL into TS 38.101-3 |
ZTE Corporation |
R4-2204774 |
TR 37.717-33 v0.7.0 |
ZTE Corporation |
9.20.2 |
UE RF requirements |
|
R4-2204749 |
TP for TR 37.717-33_DC_3A_n40A-n258A |
ZTE Corporation |
9.21.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204775 |
Revised WID on Rel-17 Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL1UL) and 3 bands NR inter-band CA (3DL1UL) |
ZTE Corporation |
R4-2204776 |
Big CR to reflect the completed DC of x bands (x=1,2,3) LTE inter-band CA (xDL1UL) and 3 bands NR inter-band CA (3DL1UL) into TS 38.101-3 |
ZTE Corporation |
R4-2204777 |
TR 37.717-11-31 v0.7.0 |
ZTE Corporation |
9.21.2 |
UE RF requirements |
|
R4-2204064 |
draft CR for DC_8_n1-n78-n257, DC_3-8_n1-n78-n257, DC_3-3-8_n1-n78-n257, DC_7-8_n1-n78-n257, DC_7-7-8_n1-n78-n257, DC_3-7-8_n1-n78-n257, DC_3-3-7-8_n1-n78-n257, DC_3-7-7-8_n1-n78-n257, DC_3-3-7-7-8_n1-n78-n257 |
CHTTL |
R4-2204067 |
TP for TR 37.717-11-31: update support of DC_3_n1-n8-n78, DC_3-3_n1-n8-n78, DC_7_n1-n8-n78, DC_7-7_n1-n8-n78 |
CHTTL |
R4-2204068 |
TP for TR 37.717-11-31: update support of DC_3-7_n1-n8-n78, DC_3-3-7_n1-n8-n78, DC_3-7-7_n1-n8-n78, DC_3-3-7-7_n1-n8-n78 |
CHTTL |
R4-2204109 |
TP for TR 37.717-11-31: EN-DC_1-8_n3-n28-n79 |
SoftBank Corp. |
R4-2204111 |
TP for TR 37.717-11-31: EN-DC_1-8_n28-n77-n79 |
SoftBank Corp. |
R4-2204117 |
TP for TR 37.717-11-31: EN-DC_8_n1-n3-n77 |
SoftBank Corp. |
R4-2204133 |
TP for TR 37.717-11-31: EN-DC_11_n3-n77-n79 |
SoftBank Corp. |
R4-2204137 |
Draft CR for 38.101-3: support of DL n77(2A) in Inter-band EN-DC of DC_1A_n3A-n77-n79A |
SoftBank Corp. |
9.22.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204675 |
Big CR introduction completed band combinations for Dual Connectivity (DC) of x bands (x=2,3,4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) |
Samsung |
R4-2204676 |
Revised WID on Dual Connectivity (DC) of x bands (x=2,3,4) LTE inter-band CA (xDL/1UL) and 1 NR FR1 band (1DL/1UL) and 1 NR FR2 band (1DL/1UL) |
Samsung |
R4-2204679 |
TR 37.717-21-22 update version 0.2.0 |
Samsung |
R4-2204701 |
TR 37.717-21-22 update version 0.2.0 |
Samsung |
9.23.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205243 |
Revised WID on Rel-17 Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL1UL) and 4 bands NR inter-band CA (4DL1UL) |
Huawei, HiSilicon |
R4-2205244 |
TR 37.717-11-41 v0.1.0 |
Huawei, HiSilicon |
R4-2205245 |
CR on Introduction of completed Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL1UL) and 4 bands NR inter-band CA (4DL1UL) into TS 38.101-1 |
Huawei, HiSilicon |
R4-2206636 |
CR on Introduction of completed Dual Connectivity (DC) of x bands (x=1,2) LTE inter-band CA (xDL1UL) and 4 bands NR inter-band CA (4DL1UL) into TS 38.101-3 |
Huawei, HiSilicon |
9.23.2 |
UE RF requirements |
|
R4-2204118 |
TP for TR 37.717-11-41: EN-DC_8_n3-n28-n77-n79 |
SoftBank Corp. |
9.24.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205238 |
Revised WID on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) |
Huawei, HiSilicon |
9.25 |
Band combinations for Uu and V2X con-current operation |
|
R4-2206445 |
TP on coexistence study of V2X_n1A-n47A, V2X_1A_n47A and V2X_n1A_47A |
CATT |
R4-2206446 |
Calculation of MSD for V2X_n1A-47A and accompanying TP |
Qualcomm Incorporated |
9.25.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2203915 |
Draft CR for TS 38.101-1, Introduce new band combinations of V2X_n1A-n47A |
CATT |
R4-2203916 |
Draft CR for TS 38.101-3, Introduce new band combination of V2X_n1A_47A and V2X_1A_n47A |
CATT |
R4-2203917 |
TR37.875, Band combinations of V2X con-current operation |
CATT |
R4-2204172 |
Big CR for 38.101-1, Introduce new band combination for V2X con-current operation |
CATT |
R4-2204173 |
Big CR for 38.101-3, Introduce new band combination for V2X con-current operation |
CATT |
R4-2206312 |
Email discussion summary for [102-e][112] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
R4-2206400 |
Draft CR for TS 38.101-1, Introduce new band combinations of V2X_n1A-n47A |
CATT |
R4-2206412 |
Email discussion summary for [102-e][112] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
R4-2206444 |
draft CR for TS 38.101-3, Introduce new band combination of V2X_n1A_47A and V2X_1A_n47A |
CATT |
9.25.2 |
UE RF requirements |
|
R4-2203913 |
TP on coexistence study of V2X_n1A-n47A, V2X_1A_n47A and V2X_n1A_47A |
CATT |
R4-2203914 |
TP on coexistence study of V2X_n8A-n47A, V2X_8A_n47A and V2X_n8A_47A |
CATT |
R4-2204014 |
Calculation of MSD for V2X_n1A-47A and accompanying TP |
Qualcomm Incorporated |
R4-2204171 |
TP for 37.875, Correction on coexistence study of V2X_3A_n47A |
CATT |
9.26 |
Adding channel bandwidth support to existing NR bands |
|
R4-2206447 |
WF on adding 100 MHz channel BW in NR-U bands n46 and n96 |
Qualcomm |
R4-2206448 |
WF on 70 and 90 MHz channel BW support for bands n48, n77 and n78 |
Rogers, AT&T, Verizon |
9.26.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205068 |
Revised Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
R4-2206313 |
Email discussion summary for [102-e][113] NR_bands_R17_BWs |
Moderator (Ericsson) |
R4-2206413 |
Email discussion summary for [102-e][113] NR_bands_R17_BWs |
Moderator (Ericsson) |
R4-2206449 |
Revised Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
9.26.2 |
UE RF requirements |
|
R4-2204548 |
n48 NS_27 30MHz BW error rel 17 CR Cat-F |
Qualcomm Incorporated |
R4-2204569 |
Draft CR for 38.101-1- Addition of 25 MHz for n28 and n83 |
CMCC |
R4-2204731 |
Draft CR to TS 38.101-1: Addition of notes for band n79 |
Samsung |
R4-2205070 |
Big CR to TS 38.101-1: Adding channel BW support in existing NR bands |
Ericsson |
9.26.2.1 |
Addition of bandwidth and Tx/Rx requirements |
|
R4-2204511 |
Clarification on UE behavior to new channel bandwidth(s) introduced in later release during initial access |
China Telecom |
R4-2205316 |
Discussion on UE support of RF channel bandwidth for bands n48_n77_n78 |
Rogers Communications Canada, AT&T |
9.26.2.2 |
NR-U 100MHz bandwidth |
|
R4-2203537 |
Further discussion on co-existence proposals between NR-U 100 MHz channel raster and Wi-Fi channel bonding in n46 (5 GHz) |
Charter Communications, Inc |
R4-2203667 |
On intra-carrier guard bands for the 100MHz NR-U channel |
Apple |
R4-2204471 |
NR-U 100 MHz channelization in band n46 |
Qualcomm Incorporated |
R4-2205822 |
Views on NR-U 100MHz in n46 |
Intel Corporation |
9.26.3 |
BS RF requirements |
|
R4-2204568 |
Draft CR for 38.104-Addition of 25 MHz for n28 |
CMCC |
R4-2204732 |
Draft CR to TS 38.104: Addition of notes for band n79 |
Samsung |
R4-2205069 |
Big CR to TS 38.104: Adding channel BW support in existing NR bands |
Ericsson |
9.27 |
Introduction of bandwidth combination set 4 (BCS4) for NR |
|
R4-2206450 |
WF on improvements to MSD table |
Huawei, HiSilicon |
R4-2206453 |
CR to TS 38.307 on Release independence of BCS4 and BCS5 |
ZTE Corporation, Huawei, HiSilicon |
9.27.2 |
UE RF requirements for BCS4/BCS5 |
|
R4-2203997 |
CR to TS 38.307 on Release independence of BCS4 and BCS5 |
ZTE Corporation |
R4-2204053 |
Discussion on the number of test points for the MSD table improvement |
CHTTL |
R4-2204486 |
Max aggregated CBW for BCS4/5 |
Nokia, Nokia Shanghai Bell |
R4-2204509 |
Discussion on maximum aggregated channel bandwidth for BCS4/5 |
Qualcomm Incorporated |
R4-2205117 |
Discussion on the maximum aggregated bandwidth of intra-band CA for BCS4/5 |
Xiaomi |
R4-2205118 |
TP for TR 38.862 to correct the maximum aggregated bandwidth for intra-band C CA with BCS4/BCS5 |
Xiaomi |
R4-2205280 |
Discussion on simplifying extended MSD table |
Huawei, HiSilicon |
R4-2205281 |
CR for 38.307 to introduce release independent method for BCS4/5 |
Huawei, HiSilicon |
R4-2205282 |
Draft CR for 38.101-1 to introduce new tables for MSD due to cross band isolation |
Huawei, HiSilicon |
R4-2206142 |
MSD Tables Simplification Proposal for BCS4 |
Skyworks Solutions Inc. |
R4-2206314 |
Email discussion summary for [102-e][114] NR_BCS4_MSD_Inter_Band_ENDC |
Moderator (Huawei) |
R4-2206414 |
Email discussion summary for [102-e][114] NR_BCS4_MSD_Inter_Band_ENDC |
Moderator (Huawei) |
R4-2206451 |
Big CRs to TS 38.101-1 for NR_BCS4 |
Huawei, HiSilicon |
R4-2206452 |
Big CRs to TS 38.101-3 for NR_BCS4 |
Nokia |
R4-2206454 |
Draft CR for 38.101-1 to introduce new tables for MSD due to cross band isolation |
Huawei, HiSilicon |
9.28.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205283 |
CR for 38.101-3 to introduce MSD requirements for missing bandwidths. |
Huawei, HiSilicon |
9.29.1 |
General |
|
R4-2205849 |
TR 37.828 v0.2.0 |
Nokia, Nokia Shanghai Bell |
R4-2206315 |
Email discussion summary for [102-e][115] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
R4-2206415 |
Email discussion summary for [102-e][115] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
R4-2206455 |
CR to TS 38.101-1 on PC1 MPR table |
Nokia |
9.29.2.1 |
Coexistence study between B5 and adjacent bands |
|
R4-2203648 |
TP to TR 37.828: Coexistence study for High-power UE Vs adjacent channel Public Safety operation for fixed-wireless/vehicle-mounted use cases in Band 5 and Band n5 |
Nokia, Nokia Shanghai Bell |
9.29.2.3 |
Filter with smaller duplex for B13, n13 and n71 |
|
R4-2205926 |
TP for TR 37.828: Filter and PA data for n71, n26 and n12 |
T-Mobile USA |
R4-2206456 |
TP for TR 37.828: Filter and PA data for n71, n26 and n12 |
T-Mobile USA |
9.29.3.2 |
UE Tx requirements (MOP, MPR, A-MPR, and ACLR) |
|
R4-2204786 |
TP to 37.828: FWA MPR |
Nokia |
R4-2205670 |
MPR studies for PCI FWA UEs |
Huawei Technologies France |
9.30 |
High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink |
|
R4-2204196 |
Draft TR 38.841 v0.6.0: High power UE for NR inter-band Carrier Aggregation with 2 bands downlink and x bands uplink (x =1,2) |
China Telecom |
R4-2204197 |
Big CR to 38.101-1 Introduce RF requirements for HPUE CA with 2 bands downlink and x bands uplink (x =1,2) |
China Telecom |
R4-2206457 |
Revised WID: High power UE for NR inter-band Carrier Aggregation with 2 bands downlink and x bands uplink (x =1,2 |
China Telecom |
9.30.2 |
UE RF requirements |
|
R4-2203631 |
Draft CR to 38.101-1 Correct the descriptions on power class requirements applications for UE maximum output power for CA |
China Telecom Corporation Ltd. |
R4-2203830 |
TP for TR 38.841: CA_n66-n77 |
Verizon Denmark |
R4-2205725 |
TP for TR 38.841 to add CA_n5-n78 |
Ericsson, Telstra |
R4-2205726 |
TP for TR 38.841 to add CA_n7-n78 |
Ericsson, Telstra |
R4-2205727 |
TP for TR 38.841 to add CA_n28-n78 |
Ericsson, Telstra |
R4-2205927 |
Draft CR for 38.101-1: Corrections related to PC2 and PC1.5 with DL CA |
T-Mobile USA, Interdigital, Skyworks Solutions, Inc. |
R4-2205928 |
TP for TR38.841: PC2 and PC1.5 n77 for CA_n25A-n77A |
T-Mobile USA |
R4-2205929 |
TP for TR38.841: PC2 and PC1.5 n77 for CA_n41A-n77A |
T-Mobile USA |
R4-2205930 |
TP for TR38.841: PC2 and PC1.5 n77 for CA_n66A-n77A |
T-Mobile USA |
R4-2205931 |
TP for TR38.841: PC1.5 n77 for CA_n71A-n77A |
T-Mobile USA |
R4-2205932 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for combinations with n25 and n77 |
T-Mobile USA |
R4-2205933 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for combinations with n41 and n77 |
T-Mobile USA |
R4-2205934 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for combinations with n66 and n77 |
T-Mobile USA |
R4-2205935 |
Draft CR for 38.101-1: Addition of n77 PC1.5 for DL CA_n71A-n77A |
T-Mobile USA |
R4-2206316 |
Email discussion summary for [102-e][116] NR_PC2_SUL_CA_lowMSD |
Moderator (China Telecom) |
R4-2206416 |
Email discussion summary for [102-e][116] NR_PC2_SUL_CA_lowMSD |
Moderator (China Telecom) |
R4-2206458 |
Draft CR to 38.101-1 Correct the descriptions on power class requirements applications for UE maximum output power for CA |
China Telecom Corporation Ltd. |
R4-2206459 |
TP for TR 38.841: CA_n2-n77 |
Verizon Denmark |
R4-2206460 |
TP for TR 38.841: CA_n66-n77 |
Verizon Denmark |
R4-2206461 |
TP for TR 38.841 to add CA_n7-n78 |
Ericsson, Telstra |
R4-2206462 |
TP for TR 38.841 to add CA_n28-n78 |
Ericsson, Telstra |
R4-2206463 |
Draft CR for 38.101-1: Corrections related to PC2 and PC1.5 with DL CA |
T-Mobile USA, Interdigital, Skyworks Solutions, Inc. |
R4-2206464 |
TP for TR38.841: PC2 and PC1.5 n77 for CA_n25A-n77A |
T-Mobile USA |
R4-2206465 |
TP for TR38.841: PC2 and PC1.5 n77 for CA_n66A-n77A |
T-Mobile USA |
R4-2206466 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for combinations with n25 and n77 |
T-Mobile USA |
R4-2206467 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for combinations with n66 and n77 |
T-Mobile USA |
R4-2206565 |
TP on pending issues for optimizations of Pi/2 BPSK uplink power |
Qualcomm |
R4-2206599 |
TP on pending issues for optimizations of Pi/2 BPSK uplink power |
Qualcomm |
9.31.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204164 |
Revised WID on High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band |
China Unicom |
R4-2204166 |
Big CR on introduction of completed PC2 for EN-DC with 1 LTE band + 1 NR TDD band |
China Unicom |
R4-2204168 |
TR 37.826 v1.1.0 ENDC_UE_PC2_R17_NR_TDD |
China Unicom |
R4-2206317 |
Email discussion summary for [102-e][117] NR_PC2_EN-DC |
Moderator (Ericsson) |
R4-2206417 |
Email discussion summary for [102-e][117] NR_PC2_EN-DC |
Moderator (Ericsson) |
9.31.2 |
UE RF requirements |
|
R4-2205714 |
TP for TR 37.826 to add DC_28_n78 |
Ericsson, Telstra |
R4-2206272 |
TP for TR 37.826 to add DC_28_n78 |
Ericsson, Telstra |
9.32.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204074 |
draft TR 38.842 v0.3.0 |
Huawei, HiSilicon, China Unicom |
R4-2204075 |
Revised WID on NR_UE_PC2_R17_CADC_SUL_xBDL_yBUL |
Huawei, HiSilicon, China Unicom |
R4-2204076 |
Big CR to 38.101-1 Introduce RF requirements for HPUE CA |
Huawei, HiSilicon, China Unicom |
9.32.2 |
UE RF requirements |
|
R4-2203829 |
TP for TR 38.841: CA_n2-n77 |
Verizon Denmark |
R4-2204018 |
TP for TR 38.842 Addition of CA_n2-n29-n77 |
AT&T |
R4-2204019 |
TP for TR 38.842 Addition of CA_n2-n66-n77 |
AT&T |
R4-2204020 |
TP for TR 38.842 Addition of CA_n5-n29-n77 |
AT&T |
R4-2204021 |
TP for TR 38.842 Addition of CA_n5-n66-n77 |
AT&T |
R4-2204022 |
TP for TR 38.842 Addition of CA_n29-n30-n77 |
AT&T |
R4-2204023 |
TP for TR 38.842 Addition of CA_n29-n66-n77 |
AT&T |
R4-2204024 |
DraftCR 38.101-1 Addition of PC2 CA Combinations |
AT&T |
R4-2204218 |
PC2 MSD NRCA 3DL 2UL for TR 38.842 |
Qualcomm Incorporated |
R4-2205728 |
TP for TR 38.842 to add CA_n5-n7-n78 |
Ericsson, Telstra |
R4-2205729 |
TP for TR 38.842 to add CA_n7-n28-n78 |
Ericsson, Telstra |
R4-2206468 |
TP for TR 38.842 Addition of CA_n2-n66-n77 |
AT&T |
R4-2206469 |
TP for TR 38.842 to add CA_n5-n7-n78 |
Ericsson, Telstra |
R4-2206470 |
TP for TR 38.842 to add CA_n7-n28-n78 |
Ericsson, Telstra |
9.33.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205677 |
Revised WID EN-DC PC2 |
Ericsson |
R4-2205683 |
Big CR 38.101-3 EN-DC PC2 |
Ericsson |
R4-2205687 |
TR 37.827 v0.4.0 ENDC_PC2_R17_xLTE_yNR |
Ericsson |
9.33.2 |
UE RF requirements |
|
R4-2204025 |
DraftCR 38.101-3 Addition of PC2 EN-DC Combinations |
AT&T |
R4-2204219 |
PC2 MSD ENDC xLTE yNR for TR 37.827 |
Qualcomm Incorporated |
R4-2205715 |
TP for TR 37.827 to add DC_3-7_n78 |
Ericsson, Telstra |
R4-2205716 |
TP for TR 37.827 to add DC_3-28_n78 |
Ericsson, Telstra |
R4-2205717 |
TP for TR 37.827 to add DC_7-28_n78 |
Ericsson, Telstra |
R4-2205718 |
draft CR 38.101-3 to add DC_3-7-28_n78 PC2 |
Ericsson, Telstra |
R4-2205719 |
TP for TR 37.827 to add DC_3_n5-n78 |
Ericsson, Telstra |
R4-2205720 |
TP for TR 37.827 to add DC_7_n5-n78 |
Ericsson, Telstra |
R4-2205721 |
draft CR 38.101-3 to add DC_3-7_n5-n78 PC2 |
Ericsson, Telstra |
R4-2205722 |
TP for TR 37.827 to add DC_3_n28-n78 |
Ericsson, Telstra |
R4-2205723 |
TP for TR 37.827 to add DC_7_n28-n78 |
Ericsson, Telstra |
R4-2205724 |
draft CR 38.101-3 to add DC_3-7_n28-n78 PC2 |
Ericsson, Telstra |
R4-2206273 |
TP for TR 37.827 to add DC_3-7_n78 |
Ericsson, Telstra |
R4-2206274 |
TP for TR 37.827 to add DC_7-28_n78 |
Ericsson, Telstra |
R4-2206275 |
TP for TR 37.827 to add DC_3_n5-n78 |
Ericsson, Telstra |
R4-2206276 |
TP for TR 37.827 to add DC_7_n5-n78 |
Ericsson, Telstra |
R4-2206277 |
TP for TR 37.827 to add DC_3_n28-n78 |
Ericsson, Telstra |
R4-2206278 |
TP for TR 37.827 to add DC_7_n28-n78 |
Ericsson, Telstra |
9.35 |
Increasing UE power high limit for CA and DC |
|
R4-2206471 |
LS on Signaling of increased maximum output power for inter-band CA and DC |
Qualcomm, InterDigital |
9.35.1 |
General |
|
R4-2203688 |
Increasing UE power high limit for CA and DC |
Apple |
R4-2204084 |
Draft LS to RAN2 on new Tx power limit for NR inter-band CA |
Huawei, HiSilicon |
R4-2205177 |
LS on new power class for inter-band UL CA and DC |
Apple |
R4-2206318 |
Email discussion summary for [102-e][118] NR_Power_Limit_CA_DC |
Moderator (Qualcomm) |
R4-2206418 |
Email discussion summary for [102-e][118] NR_Power_Limit_CA_DC |
Moderator (Qualcomm) |
9.35.2 |
Feasibility and impact study |
|
R4-2204082 |
On Power class ambiguity and new power limit for NR inter-band CA |
Huawei, HiSilicon |
R4-2204608 |
Draft LS to RAN2 on increasing UE power high limit for CA and DC |
Ericsson |
R4-2204763 |
On increasing UE maximum power for NR uplink inter band CA |
ZTE Corporation |
R4-2204825 |
R17 UE power class high limit |
OPPO |
R4-2204939 |
Further discussion on the increasing UE power high limit for CA and DC |
vivo |
9.35.3 |
UE RF requirements |
|
R4-2203555 |
RF requirements proposals for Increased MOP for CA and DC |
InterDigital Finland Oy |
R4-2203556 |
Draft CR for Introduction of the Increased MOP for CA and DC feature |
InterDigital Finland Oy |
R4-2204083 |
Draft CR to TS38101-1 Addition of higher power limit for NR inter-band CA |
Huawei, HiSilicon |
R4-2204734 |
UE RF requirements for the sum method |
Nokia, Nokia Shanghai Bell |
R4-2204814 |
Discussion on increasing UE maximum power high limit |
Xiaomi |
R4-2205450 |
Discussion on increasing power limit of CA and DC |
NTT DOCOMO INC. |
R4-2205865 |
Valid 1Tx and 2Tx configurations for increased power option for inter-band CA |
Skyworks Solutions Inc. |
R4-2206106 |
Increasing the maximum power limit for inter-band UL CA |
Qualcomm Incorporated |
R4-2206472 |
Draft CR for Introduction of the Increased MOP for CA and DC feature |
InterDigital Finland Oy |
R4-2206473 |
Increasing the maximum power limit for inter-band UL CA |
Qualcomm Incorporated |
9.36 |
High power UE (power class 2) for NR FDD band |
|
R4-2206476 |
LS on hybrid duplex operation for PC2 FDD bands |
Apple |
9.36.1 |
General |
|
R4-2204762 |
CR to TS38.307: Release independent for PC2 FDD bands |
ZTE Corporation,China Unicom |
R4-2206319 |
Email discussion summary for [102-e][119] NR_PC2_UE_FDD |
Moderator (China Unicom) |
R4-2206419 |
Email discussion summary for [102-e][119] NR_PC2_UE_FDD |
Moderator (China Unicom) |
9.36.2 |
UE RF requirements |
|
R4-2203690 |
On hybrid HD/FD operation for PC2 FDD |
Apple |
R4-2205178 |
LS on hybrid duplex operation for PC2 FDD bands |
Apple |
R4-2206474 |
LS on hybrid duplex operation for PC2 FDD bands |
Apple |
9.36.2.1 |
UE maximum output power and power tolerance |
|
R4-2204761 |
CR to TS38.101-1: Corrections on MOP tolerance for PC2 FDD n3 |
ZTE Corporation,China Unicom |
9.36.2.2 |
A-MPR requirements |
|
R4-2204081 |
CR to TS38101-1 Addition of PC2 A-MPR for FDD PC2 |
Huawei, HiSilicon, China Unicom |
R4-2204221 |
PC2_FDD NS_05 AMPR |
Qualcomm Incorporated |
R4-2206096 |
Bandwidth Parts for Reducing A-MPR for Wideband Carriers |
Lenovo |
R4-2206475 |
CR to TS38101-1 Addition of PC2 A-MPR for FDD PC2 |
Huawei, HiSilicon, China Unicom |
9.36.2.3 |
PC2 MSD requirements (investigation for HD-FDD) |
|
R4-2203691 |
HPUE (PC2) REFSENS for n1 and n3 |
Apple |
R4-2204079 |
On Remaining Issues for PC2 FDD bands |
Huawei, HiSilicon |
R4-2204080 |
CR to TS38101-1 Addition of MSD for FDD PC2 |
Huawei, HiSilicon, China Unicom |
R4-2204203 |
On MSD mitigation for FDD HPUE |
China Unicom |
R4-2204205 |
CR on power class fallback for FDD HPUE with high MSD |
China Unicom |
R4-2204223 |
PC2_n3_REFSENS_1TX_2TX |
Qualcomm Incorporated |
R4-2204764 |
On HPUE FDD band n3 MSD |
ZTE Corporation |
R4-2204813 |
Discussion on HP UE for FDD bands |
Xiaomi |
R4-2204938 |
Further discussion on MSD mitigation of FDD HPUE |
vivo |
R4-2206143 |
Reference Sensitivity Degradation for Band n3 PC2 |
Skyworks Solutions Inc. |
R4-2206477 |
CR on power class fallback for FDD HPUE with high MSD |
China Unicom |
R4-2206478 |
CR to TS38101-1 Addition of MSD for FDD PC2 |
Huawei, HiSilicon, China Unicom |
9.37 |
Additional NR bands for UL-MIMO |
|
R4-2206320 |
Email discussion summary for [102-e][120] LTE_NR_Other_WI |
Moderator (Huawei) |
R4-2206420 |
Email discussion summary for [102-e][120] LTE_NR_Other_WI |
Moderator (Huawei) |
R4-2206479 |
WF on simultaneous Rx/Tx capability |
Huawei, HiSilicon |
R4-2206481 |
WF on MPR and A-MPR requirements for PC5 NR-U UL MIMO |
Skyworks |
9.37.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205592 |
Big CR for TS38.101-1: introduction of new UL MIMO bands |
Huawei, HiSilicon |
R4-2205593 |
revised WID Basket UL MIMO bands |
Huawei, HiSilicon |
R4-2206483 |
revised WID Basket UL MIMO bands |
Huawei, HiSilicon |
R4-2206575 |
Big CR for TS38.101-1: introduction of new UL MIMO bands |
Huawei, HiSilicon |
9.37.2 |
UE RF requirements |
|
R4-2203813 |
Draft CR to 38.101-1 for adding support NR band n77 with UL-MIMO for PC1.5 UPUE |
Verizon Denmark |
R4-2204092 |
Introducing missing MPR for NR-U PC5 UL MIMO |
Skyworks Solutions Inc. |
R4-2204093 |
Draft CR TS 38.101-1: Introducing missing MPR for NR-U PC5 UL MIMO |
Skyworks Solutions Inc. |
R4-2204926 |
CR for n24 and n99 UL-MIMO PC3 |
Ligado Networks |
R4-2206482 |
Draft CR to 38.101-1 for adding support NR band n77 with UL-MIMO for PC1.5 UPUE |
Verizon Denmark |
9.39 |
Simultaneous Rx/Tx band combinations for CA, SUL, MR-DC and NR-DC |
|
R4-2205439 |
Draft CR for clarification on per band pair simultaneous RxTx capability for CA and SUL for TS 38.101-1 |
NTT DOCOMO INC. |
R4-2205440 |
Draft CR for clarification on per band pair simultaneous RxTx capability for CA and SUL for TS 38.101-1 |
NTT DOCOMO INC. |
R4-2205444 |
Draft CR for clarification on per band pair simultaneous RxTx capability for CA and SUL for TS 38.101-1 |
NTT DOCOMO INC. |
R4-2205446 |
Draft CR for clarification on per band pair simultaneous RxTx capability for TS 38.101-3 |
NTT DOCOMO INC. |
R4-2205447 |
Draft CR for clarification on per band pair simultaneous RxTx capability for TS 38.101-3 |
NTT DOCOMO INC. |
R4-2205448 |
Draft CR for clarification on per band pair simultaneous RxTx capability for TS 38.101-3 |
NTT DOCOMO INC. |
R4-2205449 |
Draft CR for clarification on per band pair simultaneous RxTx capability for DC TS 38.101-1 |
NTT DOCOMO INC. |
R4-2206486 |
Draft CR for clarification on per band pair simultaneous RxTx capability for TS 38.101-3 |
NTT DOCOMO INC. |
R4-2206487 |
Draft CR for clarification on per band pair simultaneous RxTx capability for DC TS 38.101-1 |
NTT DOCOMO INC. |
9.39.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2203684 |
draft CR to 38.101-1 on new column for mandatory simultaneous RxTx |
Apple |
R4-2203685 |
draft CR to 38.101-3 on new column for mandatory simultaneous RxTx |
Apple |
R4-2205579 |
TR 38.839 v0.2.0 |
Huawei, HiSilicon |
R4-2206484 |
draft CR to 38.101-1 on new column for mandatory simultaneous RxTx |
Apple |
R4-2206488 |
TR 38.839 v0.2.0 |
Main Session |
9.39.2 |
MSD threshold principle |
|
R4-2203683 |
MSD threshold for simultaneous Rx/Tx |
Apple |
R4-2204212 |
Discussion on the simultaneous Rx/Tx capability for FR1+FR1 FDD-TDD band combination |
SoftBank Corp. |
R4-2204741 |
Simultaneous RxTx capability for FR1+FR1 FDD-TDD band combination |
ZTE Corporation |
R4-2204815 |
Discussion on principle for simultaneous Rx Tx band combinations for CA, SUL, MR-DC and NR-DC |
Xiaomi |
R4-2205580 |
Further consideration on the simultaneous Rx/Tx capability for FR1 TDD-FDD |
Huawei, HiSilicon |
R4-2205581 |
TP for TR 38.839: update for simultaneous RxTx capability |
Huawei, HiSilicon |
R4-2206489 |
TP for TR 38.839: update for simultaneous RxTx capability |
Huawei, HiSilicon |
9.39.3 |
FR2 band combinations with simultaneous Rx/Tx |
|
R4-2203700 |
Simultaneous Rx/Tx for DL inter-band CA |
Apple |
R4-2204222 |
Recap on no support of FR2 simultaneous TxRx discussion |
MediaTek Beijing Inc. |
R4-2204742 |
Draft CR to TS 38.101-2: On Simultaneous RxTx capability for FR2 inter-band CA |
ZTE Corporation |
R4-2204743 |
Draft CR to TS 38.101-2: On Simultaneous RxTx capability for FR2 inter-band CA |
ZTE Corporation |
R4-2204744 |
Draft CR to TS 38.101-2: On Simultaneous RxTx capability for FR2 inter-band CA CA_n257-n259 and CA_n258-n260 |
ZTE Corporation |
9.40.1 |
UE RF requirements (delta_R_IB,4Rx) |
|
R4-2204048 |
CR for 4 Rx antenna ports support of band n8 |
CHTTL, China Unicom, ZTE, SGS Wireless |
R4-2206321 |
Email discussion summary for [102-e][121] NR_4Rx_Bn8_FWA |
Moderator (OPPO) |
R4-2206421 |
Email discussion summary for [102-e][121] NR_4Rx_Bn8_FWA |
Moderator (OPPO) |
R4-2206629 |
CR for release independent for 4Rx support for NR band |
CHTTL, China Unicom, ZTE |
R4-2206630 |
CR for release independent for 4Rx support for NR band |
CHTTL, China Unicom, ZTE |
R4-2206631 |
CR for release independent for 4Rx support for NR band |
CHTTL, China Unicom, ZTE |
9.40.2 |
Release independency |
|
R4-2204049 |
Further discussion on release independent for 4Rx support for NR band |
CHTTL, China Unicom, ZTE |
R4-2204050 |
draft CR for release independent for 4Rx support for NR band |
CHTTL, China Unicom, ZTE |
R4-2204051 |
draft CR for release independent for 4Rx support for NR band |
CHTTL, China Unicom, ZTE |
R4-2204052 |
draft CR for release independent for 4Rx support for NR band |
CHTTL, China Unicom, ZTE |
10.1.1 |
General |
|
R4-2203576 |
Our Status (SGS TW) for the 3GPP RAN4 5G FR1 SA MIMO OTA Lab Alignment Activity |
SGS Wireless |
R4-2204945 |
3GPP TS 38.151 v0.8.0 |
vivo |
R4-2204951 |
Further views on framework for FR1 MIMO OTA lab alignment activity |
vivo |
R4-2207300 |
WF on NR MIMO OTA |
vivo, CAICT |
R4-2207455 |
3GPP NR FR1 MIMO OTA Lab Alignment Activity Template |
CAICT |
10.1.2.1 |
Performance Requirements for FR1 |
|
R4-2204089 |
On pass or fail criteria for MIMO OTA lab alignment |
Huawei Tech.(UK) Co.. Ltd |
R4-2204571 |
Discussion on mechanical mode of FR1 MIMO OTA performance |
Samsung |
R4-2204949 |
Further views on Pass/Fail limit for FR1 MIMO OTA lab alignment activity |
vivo |
R4-2204986 |
Views on how to avoid the same UE model measured in labs |
OPPO |
R4-2204987 |
Views on Pass/Fail limit for lab alignment |
OPPO |
R4-2205035 |
Framework for FR1 MIMO OTA performance test campaign |
CAICT, vivo |
R4-2207302 |
Framework for FR1 MIMO OTA performance test campaign |
CAICT, vivo |
10.1.2.2 |
Performance Requirements for FR2 |
|
R4-2204499 |
On FR2 MIMO OTA requirements |
Qualcomm Incorporated |
R4-2204500 |
Summary results for FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2205002 |
Discussion FR2 MIMO OTA performance requirements |
Huawei,HiSilicon |
10.1.2.3 |
MU assessment for FR1 and FR2 |
|
R4-2204501 |
On preliminary MU assessment for FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2204948 |
TP to TS38.151 on FR1 MPAC MU budget |
vivo |
R4-2205003 |
Discussion on preliminary MU assessment for FR2 MIMO OTA |
Huawei,HiSilicon |
R4-2207301 |
On preliminary MU assessment for FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2207306 |
TP to TS38.151 on FR1 MPAC MU budget |
vivo |
10.1.3.1 |
Testing parameters for Performance |
|
R4-2204572 |
TP to TS 38.151 on FR1 MIMO OTA test parameter |
Samsung |
R4-2205131 |
On FR1 lab alignment |
Xiaomi |
10.1.3.3 |
Channel model validation |
|
R4-2203696 |
FR1 MIMO OTA Lab Alignment, Channel Model Validation update |
Apple, MVG |
R4-2204570 |
PDP validation results for CDL-C UMa and reference values for Umi |
CMCC |
R4-2204950 |
TP to TS38.151 on channel model validation limits |
vivo, CAICT, Spirent |
R4-2204985 |
PDP pass/fail limit for FR1 |
OPPO |
R4-2205036 |
Views on PDP reference and pass/fail limits for FR1 MIMO OTA channel model validation |
CAICT, SAICT |
R4-2205130 |
On channel model validation |
Xiaomi |
R4-2205181 |
TP to TS38.151 on FR1 Temporal Correlation Validation – Time domain technique |
MVG Industries |
R4-2205236 |
Channel Emulator BW Impact on PDP validation targets and pass/fail |
Spirent Communications |
R4-2205621 |
On FR1 Channel Model Validation |
Keysight Technologies UK Ltd |
R4-2207303 |
Views on PDP reference and pass/fail limits for FR1 MIMO OTA channel model validation |
CAICT, SAICT |
R4-2207304 |
On FR1 Channel Model Validation |
Keysight Technologies UK Ltd |
R4-2207307 |
TP to TS38.151 on channel model validation limits |
vivo, CAICT, Spirent |
R4-2207308 |
TP to TS38.151 on FR1 Temporal Correlation Validation – Time domain technique |
MVG Industries |
10.2 |
Introduction of UE TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements and test methodologies for FR1 (NR SA and EN-DC) |
|
R4-2205491 |
TR 38.834 v0.4.0 |
OPPO |
R4-2207317 |
Updated Working procedure for TRP TRS requirement development |
Vivo |
10.2.1 |
General and work plan |
|
R4-2203641 |
on number of test devices |
Huawei Tech.(UK) Co.. Ltd |
R4-2204952 |
3GPP TS 38.161 v0.2.0 |
vivo |
R4-2204953 |
Proposals for concluding the core part work of TRP TRS WI |
vivo, Apple, CAICT |
R4-2204954 |
Rapporteur input to TR 38.834 |
vivo |
R4-2204988 |
Discussion and TP on performance metrics |
OPPO |
R4-2205174 |
TP to 38.161 on general aspects |
Apple, vivo |
R4-2205175 |
TP to 38.161 on TRP aspects |
Apple, Huawei, HiSilicon, OPPO, vivo |
R4-2205826 |
TP to TR 38.834 on contents for Annex B |
ROHDE & SCHWARZ |
R4-2207152 |
Email discussion summary for [102-e][335] FR1_TRP_TRS_Part1 |
Moderator (Vivo) |
R4-2207321 |
Discussion and TP on performance metrics |
OPPO |
R4-2207323 |
TP to 38.161 on TRP aspects |
Apple, Huawei, HiSilicon, OPPO, vivo |
R4-2207326 |
WF on FR1 TRP TRS |
Vivo |
R4-2207327 |
TRP/TRS Lab Alignment Campaign Template |
Vivo |
R4-2207328 |
WF on FR1 TRP TRS for UE with multi-antenna and test time reduction |
OPPO |
R4-2207425 |
Email discussion summary for [102-e][335] FR1_TRP_TRS_Part1 |
Moderator (Vivo) |
10.2.2 |
Test methodology |
|
R4-2205234 |
TP to TR 38.834: addition of RC in test methodology |
SRTC, Bluetest |
R4-2205237 |
Discussion on the addition of RC in test methodology |
SRTC, Bluetest |
10.2.2.1 |
SA test methodology |
|
R4-2203639 |
TP on environment Annex for TS38.161 |
Huawei Tech.(UK) Co.. Ltd |
R4-2203640 |
TP to TS 38.161 on frequency bands |
Huawei Tech.(UK) Co.. Ltd |
R4-2204956 |
Workplan for altenative test methods |
vivo |
R4-2204959 |
TP to TR 38.834 on Phantom Definition |
vivo,CTIA Certification |
R4-2205645 |
TP to TR 38.834 on Ripple test procedure |
ETS-Lindgren Europe |
R4-2205731 |
TP to TR 38.834 on TRP-TRS test procedure |
ROHDE & SCHWARZ, vivo |
R4-2205814 |
TP to TR 38.834 on Measurement distance |
ROHDE & SCHWARZ, vivo |
R4-2207315 |
TP on environment Annex for TS38.161 |
Huawei Tech.(UK) Co.. Ltd |
R4-2207316 |
TP to TS 38.161 on frequency bands |
Huawei Tech.(UK) Co.. Ltd |
R4-2207318 |
Workplan for altenative test methods |
vivo |
R4-2207324 |
TP to TR 38.834 on Ripple test procedure |
ETS-Lindgren Europe |
R4-2207325 |
TP to TR 38.834 on Measurement distance |
ROHDE & SCHWARZ, vivo |
10.2.2.2 |
EN-DC test methodology |
|
R4-2203638 |
On ENDC selection |
Huawei Tech.(UK) Co.. Ltd |
R4-2203694 |
Remaining issues with EN-DC configuration for TRP/TRS |
Apple |
R4-2204573 |
Discussion on ENDC combination and measurement parameters |
Samsung |
R4-2204960 |
TP to TR 38.834 on Environmental requirements |
vivo |
R4-2204982 |
On EN-DC combinations |
OPPO |
R4-2207320 |
TP to TR 38.834 on Environmental requirements |
vivo |
10.2.2.3 |
UE with multiple antennas test methodology |
|
R4-2203637 |
on tests with TAS on |
Huawei Tech.(UK) Co.. Ltd |
R4-2203695 |
On TRP for TxD UEs |
Apple |
R4-2204508 |
TRP test method for UEs with Tx diversity |
Qualcomm Incorporated |
R4-2204981 |
Downlink Rx signal impact on TAS test method |
OPPO |
R4-2204989 |
TP to TR 38.834 on multi-antenna UE |
OPPO |
R4-2207153 |
Email discussion summary for [102-e][336] FR1_TRP_TRS_Part2 |
Moderator (OPPO) |
R4-2207329 |
TP to TR 38.834 on multi-antenna UE |
OPPO |
R4-2207426 |
Email discussion summary for [102-e][336] FR1_TRP_TRS_Part2 |
Moderator (OPPO) |
10.2.2.4 |
Test time reduction |
|
R4-2204958 |
Further discussion on Single Point Offset test method for EN-DC testing time reduction |
vivo |
R4-2204984 |
On test time reduction |
OPPO |
10.2.3.1 |
Framework for lab alignment and requirements |
|
R4-2203693 |
Remaining issues with the performance framework |
Apple |
R4-2204574 |
Discussion on FR1 TRP TRS performance requirement derivation |
Samsung |
R4-2204955 |
Updated Working procedure for TRP TRS requirement development |
vivo |
R4-2204983 |
On Framework for lab alignment activity |
OPPO |
R4-2205037 |
On TRP TRS Lab Alignment Campaign |
CAICT, SAICT |
R4-2205132 |
on On Performance test campaign |
Xiaomi |
10.2.3.2 |
SA requirements |
|
R4-2204957 |
Test lab and device information for lab alignment activity |
vivo |
R4-2204990 |
TP to TS 38.161 on Annex A: Test methodology |
OPPO |
R4-2207322 |
TP to TS 38.161 on Annex A: Test methodology |
OPPO |
10.3.1 |
General |
|
R4-2203824 |
CR on UL MIMO coherence for Tx switching |
China Telecom |
R4-2206297 |
Introduction of power limits for serving cells of UL CA |
Ercsson |
R4-2206298 |
Introduction of power limits for serving cells of UL CA |
Ercsson |
R4-2206324 |
Email discussion summary for [102-e][124] NR_RF_FR1_enh_IntraHPUE |
Moderator (Huawei) |
R4-2206424 |
Email discussion summary for [102-e][124] NR_RF_FR1_enh_IntraHPUE |
Moderator (Huawei) |
R4-2206503 |
LS on clarification of dualPA-Architecture capability |
OPPO |
R4-2206504 |
WF on Scell dropping and PHRCA |
Huawei, HiSilicon |
10.3.2.3 |
HPUE for TDD intra-band non-contiguous UL CA |
|
R4-2204225 |
1CC Fall-Back MPR for NC UL CA with 1LO Architecture |
Qualcomm Incorporated |
R4-2204827 |
R17 FR1 clarification of dualPA-architecture capability |
OPPO |
R4-2204977 |
Corrections on PC3 intra-band non-contiguous UL CA requirements for 2LO case |
vivo, Huawei, Skyworks |
R4-2204978 |
Corrections on PC3 intra-band non-contiguous UL CA requirements for 2LO case |
vivo, Huawei, Skyworks |
R4-2204979 |
Adding intra-band non-contiguous UL CA requirements for PC2 2LO and PC2&3 1LO case |
vivo, Huawei, Skyworks |
R4-2205587 |
Big CR for TS 38.101-1 introduction of PC2 intra-band non-contiguous UL CA |
Huawei, HiSilicon, Qualcomm, Skyworks, vivo |
R4-2206505 |
Adding intra-band non-contiguous UL CA requirements for PC2 2LO and PC2&3 1LO case |
vivo, Huawei, Skyworks |
10.3.2.4 |
Intra-band UL contiguous CA for UL MIMO (n41C and n78C) |
|
R4-2205588 |
Big CR for TS 38.101-1 contiguous CA with UL MIMO for power class 2 |
Huawei, HiSilicon, LG Electronics |
R4-2206506 |
Big CR for TS 38.101-1 contiguous CA with UL MIMO for power class 2 |
Huawei, HiSilicon, LG Electronics |
10.3.2.5 |
Solution preventing transmission power dropping on cell with lower priority |
|
R4-2203689 |
SCell dropping issue for UL CA |
Apple |
R4-2204966 |
Further discussion on Scell dropping |
vivo |
10.3.2.5.1 |
FR1 related |
|
R4-2204609 |
Further details on resolving the Scell dropping (power prioritization) problem by power limits: signaling |
Ericsson |
R4-2204610 |
Introduction of power limits for serving cells of UL CA |
Ericsson |
R4-2204826 |
R17 FR1 CA PHR reporting in SCC drop |
OPPO |
R4-2205589 |
On SCell dropping |
Huawei, HiSilicon |
R4-2205590 |
draft CR for TS 38.101-1 Power configuration for CA |
Huawei, HiSilicon |
10.3.2.5.2 |
FR2 related |
|
R4-2204611 |
Introduction of power limits for serving cells of UL CA |
Ericsson |
R4-2205591 |
draft CR for TS 38.101-2 Power configuration for CA |
Huawei, HiSilicon |
R4-2205885 |
Discussion on UE behavior and root cause for dropping SCell |
Qualcomm Incorporated |
10.3.3 |
RRM core requirements |
|
R4-2204887 |
Big CR: RRM requirements for Rel-17 NR FR1 RF |
Huawei, Hisilicon |
R4-2206752 |
Email discussion summary for [102-e][209] NR_RF_FR1_enh_RRM_NWM |
Moderator (Huawei) |
R4-2206835 |
Big CR: RRM requirements for Rel-17 NR FR1 RF |
Huawei, HiSilicon |
R4-2206836 |
WF on R17 NR FR1 RF enhancement RRM |
Huawei, Hisilicon |
R4-2207050 |
Email discussion summary for [102-e][209] NR_RF_FR1_enh_RRM_NWM |
Moderator (Huawei) |
10.3.4 |
RRM performance requirements |
|
R4-2204888 |
Test case for R17 Tx switching enhancement |
Huawei, Hisilicon |
10.4.1 |
General |
|
R4-2204787 |
TR 38.851 v0.4.0 |
Nokia, Nokia Shanghai Bell |
R4-2206325 |
Email discussion summary for [102-e][125] NR_RF_FR2_enh2_Part_1 |
Moderator (Nokia) |
R4-2206425 |
Email discussion summary for [102-e][125] NR_RF_FR2_enh2_Part_1 |
Moderator (Nokia) |
R4-2206507 |
WF for FR2 DL CA |
Nokia |
R4-2206508 |
WF for FR2 UL CA |
Qualcomm |
10.4.2.1 |
Inter-band DL CA requirements |
|
R4-2204361 |
Sensitivity requirements for inter-band DL CA with CBM |
NTT DOCOMO, INC. |
R4-2204789 |
Addition of downlink CA feature for CBM UEs and one band combination for IBM UEs |
Nokia, Qualcomm |
10.4.2.1.1 |
CA configurations within the same frequency group based on CBM |
|
R4-2204035 |
UE requirements for CBM for the same frequency group |
Sony, Ericsson |
R4-2204143 |
Discussion on CBM based inter-band DL CA within same frequency group |
LG Electronics |
R4-2204229 |
Fs_inter and view on FR2 inter-band DL CA within same frequency group based on CBM |
MediaTek Beijing Inc. |
R4-2204927 |
R17 FR2 CBM inter-band DL CA |
OPPO |
R4-2204940 |
Discussion on requirement of n258-n261 |
vivo |
R4-2205122 |
Discussion on inter-band DL CA with CBM |
Xiaomi |
R4-2205598 |
On RF requirements for FR2 Inter-band DL CA with CBM |
Huawei, HiSilicon |
R4-2206055 |
On delta(RIB) for n258+n261 DL inter-CA |
Qualcomm Incorporated |
10.4.2.1.2 |
CA configurations between different frequency groups based on CBM |
|
R4-2203699 |
FR2 Sensitivity requirements for inter-band CBM |
Apple |
R4-2204036 |
Requirements for CBM UEs between different frequency group |
Sony, Ericsson |
R4-2204230 |
Reference signal, and relaxation value about FR2 inter-band DL CA between different frequency groups based on CBM |
MediaTek Beijing Inc. |
R4-2204575 |
Discussion on requirements of FR2 inter-band DL CA |
Samsung |
R4-2204612 |
Introduction of requirements for DL inter-band CA for CBM-capable UEs |
Ericsson, Sony |
R4-2204941 |
Discussion on CBM between different frequency group |
vivo |
R4-2206056 |
On delta(RIB) for DL inter-CA with CBM in n260+n261 |
Qualcomm Incorporated |
10.4.2.1.4 |
Rx beam switch value |
|
R4-2204790 |
Discussion on UE Rx beam switch delay |
Nokia, Nokia Shanghai Bell |
10.4.2.2.1 |
Inter-band UL CA for two bands |
|
R4-2203814 |
Introduce FR2 n260 and n261 uplink CA |
Verizon Denmark |
R4-2204037 |
UE UL CA requirements based on IBM |
Sony, Ericsson |
R4-2204576 |
Discussion on MOP relaxation of FR2 inter-band UL CA |
Samsung |
R4-2205123 |
Tx requirements for inter-band UL CA between different frequency groups based on IBM |
Xiaomi |
R4-2205599 |
On RF requirements for FR2 inter-band UL CA |
Huawei, HiSilicon |
R4-2206057 |
Draft CR to 38.101-2 FR2+FR2 ULCA |
Qualcomm, Nokia, Verizon, Docomo |
R4-2206579 |
Draft CR to 38.101-2 FR2+FR2 ULCA |
Qualcomm, Nokia, Verizon, Docomo |
R4-2206597 |
Draft CR to 38.101-2 FR2+FR2 ULCA |
Qualcomm, Nokia, Verizon, Docomo |
R4-2206600 |
Draft CR to 38.101-2 FR2+FR2 ULCA |
Qualcomm, Nokia, Verizon, Docomo |
10.4.2.2.2 |
CA configuration CA_n257A-n259A based on IBM |
|
R4-2204228 |
View on FR2 inter-band UL CA relaxation |
MediaTek Beijing Inc. |
R4-2204928 |
R17 FR2 Inter-band UL CA requirements |
OPPO |
R4-2204942 |
Discussion on iinter-band UL CA |
vivo |
R4-2205109 |
Discussion on relaxation value X&Y for CA_n257A_n259A |
ZTE Corporation |
R4-2206054 |
delta(TIB) for FR2+FR2 ULCA |
Qualcomm Incorporated |
10.4.3 |
UL gaps for self-calibration and monitoring |
|
R4-2204943 |
Discussion on UL gap |
vivo |
R4-2206509 |
WF on UL gap in FR2 |
Main Session |
R4-2206510 |
LS to RAN2 on UL gap in FR2 RF enhancement |
Apple |
R4-2206604 |
WF on UL gap in FR2 |
Main Session |
R4-2206605 |
LS to RAN2 on UL gap in FR2 RF enhancement |
Apple |
R4-2206608 |
LS to RAN2 on UL gap in FR2 RF enhancement |
Apple |
10.4.3.1 |
UE Tx power management |
|
R4-2203557 |
Requirements and test cases of UE FR2 UL Gap for UE Tx power enhancement |
Nokia Denmark |
R4-2203749 |
UL gaps for Tx power management RF aspect |
Apple |
R4-2203751 |
Draft CR for UL gap for Tx power management RF aspect |
Apple |
R4-2204613 |
More on UE Tx power management for MPE compliance |
Ericsson, Sony |
R4-2204925 |
R17 FR2 UL gap for power management |
Guangdong OPPO Mobile Telecom. |
R4-2205005 |
Discussion on Tx power management |
Huawei,HiSilicon |
R4-2206326 |
Email discussion summary for [102-e][126] NR_RF_FR2_enh2_Part_2 |
Moderator (Apple) |
R4-2206426 |
Email discussion summary for [102-e][126] NR_RF_FR2_enh2_Part_2 |
Moderator (Apple) |
R4-2206513 |
Draft CR for UL gap for Tx power management RF aspect |
Apple |
10.4.3.2 |
Coherent UL-MIMO |
|
R4-2203750 |
UL gaps for coherent UL MIMO |
Apple |
R4-2205004 |
Draft CR to 38.101-2 on requirements for coherent UL MIMO |
Huawei,HiSilicon |
R4-2205006 |
Discussion on UL coherent MIMO |
Huawei,HiSilicon |
R4-2205611 |
FR2 UL coherent MIMO |
Anritsu Limited |
R4-2206512 |
Draft CR to 38.101-2 on requirements for coherent UL MIMO |
Huawei,HiSilicon |
10.4.4 |
DC location for intra-band UL CA with > 2 CCs for both FR2 and FR1 |
|
R4-2203698 |
DC location for intra-band UL CA with more than 2 CCs |
Apple |
R4-2204198 |
Handling of multiple DC locations for intra-band configuration |
Nokia, Nokia Shanghai Bell |
R4-2204822 |
Further study on DC location reporting |
Huawei, HiSilicon |
R4-2204922 |
R17 FR2 DC reporting |
OPPO |
R4-2204944 |
Discussion and draft reply LS on DC location |
vivo |
R4-2205883 |
Two DC location and RAN2 LS discussion |
Qualcomm Incorporated |
R4-2206327 |
Email discussion summary for [102-e][127] NR_RF_FR2_enh2_Part_3 |
Moderator (Vivo) |
R4-2206427 |
Email discussion summary for [102-e][127] NR_RF_FR2_enh2_Part_3 |
Moderator (Vivo) |
R4-2206514 |
WF on DC location |
vivo |
R4-2206515 |
Reply LS on DC location for >2CC |
Qualcomm |
R4-2206601 |
WF on DC location |
Main Session |
R4-2206602 |
Reply LS on DC location for >2CC |
Qualcomm |
10.4.5 |
CA BW classes |
|
R4-2203697 |
New CA BW classes |
Apple |
R4-2206062 |
On new contiguous BW classes for legacy networks |
Qualcomm Incorporated |
10.4.5.1 |
New FR2 CA BW classes |
|
R4-2203812 |
FR2 bandwidth class and fallback group |
Verizon |
R4-2203990 |
Discussion on new FR2 CA BW classes in hybrid FBG |
ZTE Corporation |
R4-2204220 |
View on new FR2 CA BW class options |
MediaTek Beijing Inc. |
R4-2204614 |
FR2 bandwidth classes covering up to 1600 MHz aggregated bandwidth with mixed carrier bandwidths |
Ericsson |
R4-2204615 |
FR2 CA BW classes up to 1600 MHz aggregated BW with mixed channel bandwidths |
Ericsson |
R4-2204788 |
Solution to FBG3+2 topic |
Nokia, Nokia Shanghai Bell |
R4-2205124 |
Discussion on FR2 new CA BW classes |
Xiaomi |
R4-2205125 |
LS on release independence aspects of newly introduced FR2 CA BW Classes |
Xiaomi |
R4-2205126 |
Draft CR for TS 38.101-2 to introduction of FR2 new CA BW classes V, AF, GF, HF, IF, JF, KF, LF, MF,ME, MD, MA |
Xiaomi |
R4-2206556 |
Further input on performance when using the next larger channel |
Apple |
R4-2206577 |
FR2 CA BW classes up to 1600 MHz aggregated BW with mixed channel bandwidths |
Ericsson |
R4-2206578 |
LS on release independence aspects of newly introduced FR2 CA BW Classes |
Xiaomi |
10.4.6 |
RRM core requirements |
|
R4-2205868 |
Draft Big CR on RRM requirements for FR2 Inter-band CA |
Nokia, Nokia Shanghai Bell |
R4-2206753 |
Email discussion summary for [102-e][210] NR_RF_FR2_req_enh2_RRM |
Moderator (Nokia) |
R4-2206837 |
WF on RRM requirements for FR2 Inter-band DL CA and UL CA |
Nokia |
R4-2206839 |
draftCR on MRTD for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2207051 |
Email discussion summary for [102-e][210] NR_RF_FR2_req_enh2_RRM |
Moderator (Nokia) |
10.4.6.1 |
Inter-band DL CA requirements for CBM |
|
R4-2205869 |
draftCR on CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2206838 |
draftCR on CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
10.4.6.1.1 |
MRTD requirements |
|
R4-2203860 |
MRTD requirements for CBM based Inter-band DL CA |
Qualcomm Incorporated |
R4-2204149 |
Discussion on MRTD for FR2 inter-band CA based on CBM |
LG Electronics |
R4-2204182 |
Discussion on CBM MRTD requirement for FR2 inter-band DL CA |
MediaTek inc. |
R4-2204271 |
MRTD requirements for FR2 inter-band DL CA enhancements |
OPPO |
R4-2205326 |
Discussion on MRTD requirements for FR2 inter-band DL CA with CBM |
Huawei, HiSilicon |
R4-2205423 |
Timing requirements for inter-band DL CA |
Ericsson |
R4-2205424 |
Timing requirements for inter-band DL CA |
Ericsson |
R4-2205870 |
discussion on MRTD for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2205871 |
draftCR on MRTD for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
10.4.6.1.2 |
Other RRM requirements |
|
R4-2203861 |
RRM requirements for CBM based Inter-band DL CA |
Qualcomm Incorporated |
R4-2204183 |
Discussion on CBM RRM requirements for FR2 inter-band DL CA |
MediaTek inc. |
R4-2204184 |
Introduction of SCell activation delay requirement for FR2 inter-band CA with common beam management |
MediaTek inc. |
R4-2204272 |
Other RRM requirements for FR2 inter-band DL CA enhancements |
OPPO |
R4-2205327 |
Discussion on other RRM requirements for FR2 inter-band DL CA with CBM |
Huawei, HiSilicon |
R4-2205328 |
DraftCR on applicability rules for FR2 inter-band CA with CBM |
Huawei, HiSilicon |
R4-2205657 |
On network driven Rx beam switch for CBM |
Apple |
R4-2205830 |
Discussion on RRM requirements of inter-band DL CA for CBM UE |
Ericsson |
R4-2205831 |
Draft CR on scheduling restriction for FR2 inter-band DL CA for CBM UE |
Ericsson |
R4-2205872 |
discussion on other RRM requirements for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2205873 |
draftCR on measurement restriction for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2206841 |
DraftCR on applicability rules for FR2 inter-band CA with CBM |
Huawei, HiSilicon |
R4-2206842 |
Draft CR on scheduling restriction for FR2 inter-band DL CA for CBM UE |
Ericsson |
R4-2206843 |
draftCR on measurement restriction for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
10.4.6.2 |
Inter-band UL CA for IBM |
|
R4-2205832 |
Discussion on RRM requirements for inter-band UL CA for IBM UE |
Ericsson |
R4-2205833 |
Draft CR on number of UL CC support for FR2 and interruption requirements for FR2 UL CA for IBM UE |
Ericsson |
R4-2205874 |
Discussion on supportedserving carriers for IBM inter-band FR2 UL CA |
Nokia, Nokia Shanghai Bell |
R4-2205875 |
draftCR on RRM requirements for IBM inter-band FR2 UL CA |
Nokia, Nokia Shanghai Bell |
R4-2206069 |
Discussion on RRM requirements of FR2 inter-band DL and UL CA for IBM UE |
Ericsson |
10.4.6.3 |
UL gaps for self-calibration and monitoring |
|
R4-2203752 |
UL gaps for Tx power management RRM aspect |
Apple |
R4-2203753 |
Draft CR for UL gap for Tx power management RRM aspect |
Apple |
R4-2203862 |
UL gaps for self-calibration and monitoring |
Qualcomm Incorporated |
R4-2205013 |
Discussion on RRM impact of UL gap for Tx power management |
ZTE Corporation |
R4-2205649 |
Network impact of FR2 UL gaps - RRM |
Nokia, Nokia Shanghai Bell |
R4-2205650 |
LS on UL gap in FR2 RF enhancement |
Nokia, Nokia Shanghai Bell |
R4-2205834 |
Discussion on UL gaps for self calibration and monitoring |
Ericsson |
R4-2205835 |
Draft CR on UL gaps for TX power management |
Ericsson |
R4-2206511 |
Draft CR for UL gap for Tx power management RRM aspect |
Apple |
R4-2206910 |
Draft CR Minimum requirement for CSI-RS based beam failure detection for UE configured with relaxed measurement criterion |
Apple |
10.5.1 |
General |
|
R4-2205105 |
TP to TS 38.106 clause 6.8 |
ZTE Corporation |
R4-2205128 |
TP to TS 38.106 Sections 1,2, and 3 |
Qualcomm CDMA Technologies |
R4-2207154 |
Email discussion summary for [102-e][304] NR_Repeater_General |
Moderator (Qualcomm) |
R4-2207278 |
WF on TDD Repeater Switching |
Qualcomm |
R4-2207281 |
TP to TS 38.106 clause 6.8 |
ZTE Corporation |
R4-2207282 |
TP to TS 38.106 Sections 1,2, and 3 |
Qualcomm CDMA Technologies |
R4-2207427 |
Email discussion summary for [102-e][304] NR_Repeater_General |
Moderator (Qualcomm) |
R4-2207526 |
Draft TS 38.106 v0.1.0 update to include agreed TPs |
CMCC |
10.5.1.1 |
System parameters |
|
R4-2203942 |
TP for TS 38.106:Clause 4 general |
CATT |
R4-2205031 |
Repeater co-location requirements |
Ericsson |
R4-2205106 |
Discussion on co-location requirement for multi-band repeaters |
ZTE Corporation |
R4-2206050 |
System Parameters: Co-location requirements of repeaters |
Nokia, Nokia Shanghai Bell |
R4-2207279 |
TP for TS 38.106:Clause 4 general |
CATT |
10.5.1.3 |
TDD repeater switching requirements |
|
R4-2203943 |
TP for TS 38.106:ON OFF mask |
CATT |
R4-2203944 |
Discussion on TDD repeater switching requirements |
CATT |
R4-2204556 |
Discussion on switching related requirements |
CMCC |
R4-2205024 |
Repeaters TDD aspects |
Ericsson |
R4-2205107 |
Discussion on TDD repeater switching requirements |
ZTE Corporation |
R4-2205968 |
TDD Repeater switching |
Huawei |
R4-2206042 |
TDD repeater switching requirements |
Nokia, Nokia Shanghai Bell |
R4-2207280 |
TP for TS 38.106:ON/OFF mask |
CATT |
10.5.1.4 |
Others |
|
R4-2204555 |
Discussion on repeater co-located requirements |
CMCC |
R4-2205108 |
Discussion on specification drafting: OTA output intermodulation |
ZTE Corporation |
R4-2205969 |
Repeater co-location issues |
Huawei |
10.5.2 |
Conductive RF core requirements |
|
R4-2207283 |
WF on other conducted RF requirements |
Ericsson |
R4-2207284 |
WF on OOB gain and ACRR |
CMCC |
10.5.2.1 |
Transmitted power related requirements |
|
R4-2205971 |
TP to TS 38.106 clause 6.1 and 6.2 |
Huawei |
R4-2207155 |
Email discussion summary for [102-e][305] NR_Repeater_RF_Part1 |
Moderator (CMCC) |
R4-2207428 |
Email discussion summary for [102-e][305] NR_Repeater_RF_Part1 |
Moderator (CMCC) |
10.5.2.2 |
Emission requirements |
|
R4-2203945 |
Discussion on out of band gain and ACRR requirements for FR1 |
CATT |
R4-2204557 |
Discussion on repeater emission related conducted requirements |
CMCC |
R4-2205026 |
Repeater conducted emissions requirements |
Ericsson |
R4-2205203 |
TP to TS 38.106 clause 6.5 Unwanted emissions conducted |
Nokia, Nokia Shanghai Bell |
R4-2207285 |
TP to TS 38.106 clause 6.1 and 6.2 |
Huawei |
R4-2207286 |
TP to TS 38.106 clause 6.5 Unwanted emissions conducted |
Nokia, Nokia Shanghai Bell |
R4-2207394 |
TP to TS 38.101-5 on clause 7.6 Blocking characteristics |
Mediatek India Technology Pvt. |
10.5.2.3 |
Others |
|
R4-2203947 |
Discussion on NF requirement related issues |
CATT |
R4-2204558 |
Discussion on other conducted requirements for NR repeater |
CMCC |
R4-2204559 |
TP to TS 38.106 conducted EVM and input IMD |
CMCC |
R4-2205025 |
Repeater conducted requirements |
Ericsson |
R4-2205027 |
Draft TP to TS 38.106: Frequency stability and out of band gain requirements |
Ericsson |
R4-2205464 |
Further discussions on other requirements of conducted repeater |
ZTE Corporation |
R4-2205465 |
TP to TS 38.106 clause 6.9 ACRR requirement |
ZTE Corporation |
R4-2205967 |
Repeater FR1 noise equivalent requirements |
Huawei |
R4-2205970 |
Repeater FR1 OOB gain and ACRR |
Huawei |
R4-2206045 |
EVM, OOB gain and ACRR for FR1 NR Repeaters |
Nokia, Nokia Shanghai Bell |
R4-2207287 |
TP to TS 38.106 conducted EVM and input IMD |
CMCC |
R4-2207289 |
TP to TS 38.106 clause 6.9 ACRR requirement |
ZTE Corporation |
10.5.3 |
Radiated RF core requirements |
|
R4-2207290 |
WF on repeater RF requirements |
Huawei |
10.5.3.1 |
Transmitted power related requirements |
|
R4-2205030 |
Repeater radiated power requirements |
Ericsson |
R4-2205974 |
TP to TS 38.106 clause 9.1 and 9.2 |
Huawei |
R4-2207156 |
Email discussion summary for [102-e][306] NR_Repeater_RF_Part2 |
Moderator (Huawei) |
R4-2207429 |
Email discussion summary for [102-e][306] NR_Repeater_RF_Part2 |
Moderator (Huawei) |
10.5.3.2 |
Emission requirements |
|
R4-2204549 |
Views on the ACLR requirements for NR repeater for FR2 |
NTT DOCOMO, INC. |
R4-2204561 |
Discussion on repeater emission related radiated requirements |
CMCC |
R4-2205029 |
Repeaters radiated emissions requirements |
Ericsson |
R4-2205204 |
TP to TS 38.106 clause 7.5 Unwanted emissions radiated |
Nokia, Nokia Shanghai Bell |
R4-2207291 |
TP to TS 38.106 clause 9.1 and 9.2 |
Huawei |
R4-2207292 |
TP to TS 38.106 clause 7.5 Unwanted emissions radiated |
Nokia, Nokia Shanghai Bell |
10.5.3.3 |
Others |
|
R4-2203946 |
Discussion on out of band gain and ACRR requirements for FR2 |
CATT |
R4-2204560 |
TP to TS 38.106 radiated EVM and input IMD |
CMCC |
R4-2205028 |
Repeaters radiated requirements |
Ericsson |
R4-2205466 |
Further discussions on other requirements of radiated repeater |
ZTE Corporation |
R4-2205467 |
TP to TS 38.106 clause 9.9 ACRR requirement |
ZTE Corporation |
R4-2205972 |
Repeater FR2 OOB gain and ACRR |
Huawei |
R4-2205973 |
Repeater FR2 other RF |
Huawei |
R4-2206046 |
EVM, OOB gain and ACRR for FR2 NR Repeaters |
Nokia, Nokia Shanghai Bell |
R4-2207293 |
TP to TS 38.106 radiated EVM and input IMD |
CMCC |
R4-2207294 |
TP to TS 38.106 clause 9.9 ACRR requirement |
ZTE Corporation |
10.5.4 |
EMC core requirements |
|
R4-2204358 |
TP to TS38.114:Definitions, symbols and abbreviations |
ZTE Corporation |
R4-2204494 |
TS38.114V0.3.0 to capture RAN4#102-e agreements |
ZTE Corporation |
R4-2205451 |
Discussion on TDD NR repeater |
Nokia, Nokia Shanghai Bell |
10.6.4 |
BS RF conformance testing |
|
R4-2203969 |
CR for 37.145-1 on BS RF conformance testing for 1024QAM for NR FR1 |
CATT |
R4-2203970 |
CR for 37.141 on BS RF conformance testing for 1024QAM for NR FR1 |
CATT |
R4-2205019 |
CR to TS 38.141-2: Introduction of 1024 QAM in FR1 |
Ericsson |
R4-2205195 |
CR to TS 37.145-2 with 1024QAM introduction |
Nokia, Nokia Shanghai Bell |
R4-2205463 |
CR to TS 38.141-1: Introduction of 1024 QAM in FR1 |
ZTE Corporation |
R4-2207157 |
Email discussion summary for [102-e][307] NR_DL1024QAM_RF |
Moderator (Ericsson) |
R4-2207189 |
CR to TS 38.141-2: Introduction of 1024 QAM in FR1 |
Ericsson |
R4-2207430 |
Email discussion summary for [102-e][307] NR_DL1024QAM_RF |
Moderator (Ericsson) |
10.6.5 |
Demodulation and CSI requirements |
|
R4-2204332 |
Discussion on limitation of the measurement interval for the determination of the averaged EVM for FR2-2, test time improvements and possible impact on measuring uncertainties (minimal) |
ROHDE & SCHWARZ |
10.6.5.1 |
General |
|
R4-2205085 |
Update work plan for UE demodulation requirements for DL 1024QAM for NR FR1 |
Ericsson |
R4-2206075 |
PDSCH Impairment results and other requirements for 1024QAM FR1 UE Demod Tests |
Qualcomm Incorporated |
R4-2207158 |
Email discussion summary for [102-e][318] NR_DL1024QAM_Demod |
Moderator (Ericsson) |
R4-2207254 |
Way forward for NR DL1024QAM demodulationand CQI reporting requirement |
Ericsson |
R4-2207431 |
Email discussion summary for [102-e][318] NR_DL1024QAM_Demod |
Moderator (Ericsson) |
10.6.5.2 |
PDSCH requirements |
|
R4-2203760 |
Discussion on PDSCH demod requirements with 1KQAM |
Apple |
R4-2205086 |
Summary of PDSCH simulation results for DL 1024QAM in FR1 |
Ericsson |
R4-2205087 |
UE demodulation requirements for DL 1024QAM |
Ericsson |
R4-2205748 |
Discussion and simulation results on 1024QAM PDSCH |
Huawei,HiSilicon |
R4-2205904 |
Draft CR to TS38.101-4, PDSCH requirements for 1024QAM in FR1 FDD |
MediaTek inc. |
R4-2205905 |
Discussion on the PDSCH requirements for 1024QAM |
MediaTek inc. |
R4-2206001 |
Simulation results for 1024QAM PDSCH |
Intel Corporation |
10.6.5.3 |
SDR requirements |
|
R4-2203761 |
Discussion on SDR requirements with 1KQAM |
Apple |
R4-2205088 |
SDR requirements for DL 1024QAM |
Ericsson |
R4-2205749 |
Discussion and simulation results on 1024QAM SDR |
Huawei,HiSilicon |
R4-2206002 |
Discussion on SDR requirements for 1024QAM |
Intel Corporation |
10.6.5.4 |
CQI requirements |
|
R4-2205089 |
CQI reporting requirements for DL 1024QAM |
Ericsson |
R4-2205750 |
Discussion and simulation results on 1024QAM CSI |
Huawei,HiSilicon |
R4-2205751 |
Draft CR on FDD CQI reporting cases for 1024QAM and CSI RMC (TS38.101-4) |
Huawei,HiSilicon |
R4-2205906 |
Discussion on the CQI requirements for 1024QAM |
MediaTek inc. |
10.7.1 |
General |
|
R4-2204595 |
3GPP TR 38.837 v0.4.0 |
vivo |
R4-2204968 |
TP for TR 38.837 on Power Class Clarification for SA |
vivo |
R4-2205574 |
Big CR for TS 38.101-1 Tx diversity requirements (phase 2) |
Huawei, HiSilicon, Qualcomm, vivo |
R4-2205575 |
Big CR for TS 38.307: release independent requirements for TxD |
Huawei, HiSilicon |
R4-2206328 |
Email discussion summary for [102-e][128] NR_TxD |
Moderator (Qualcomm) |
R4-2206428 |
Email discussion summary for [102-e][128] NR_TxD |
Moderator (Qualcomm) |
R4-2206516 |
Big CR for TS 38.307: release independent requirements for TxD |
Huawei, HiSilicon |
10.7.2 |
UE RF requirements for phase 1 (38.101-1) |
|
R4-2206133 |
TP to TR38.837 on MPR evaluation for 2Tx PC2 and PC1.5 operation |
Skyworks Solutions Inc. |
10.7.2.1 |
UL MIMO requirement for TxD except ULFPTx |
|
R4-2205578 |
draft CR for TS 38.101-1: move 2Tx MPR to Clause 6.2D (Rel-16) |
Huawei, HiSilicon, Qualcomm |
R4-2206517 |
draft CR for TS 38.101-1: move 2Tx MPR to Clause 6.2D (Rel-16) |
Huawei, HiSilicon, Qualcomm |
10.7.3.1 |
SRS antenna switching related |
|
R4-2203681 |
TxD and SRS antenna switching |
Apple |
R4-2204616 |
Pcmax for SRS usage set as antenna switching for TxD and UL-MIMO features |
Ericsson |
R4-2204836 |
Draft R17 CR on SRS IL for TxD |
OPPO |
R4-2204837 |
R17 FR1 TP to 38.837 for TxD SRS IL |
OPPO |
R4-2204921 |
R17 FR1 SRS IL for TxD and ULFPTx |
OPPO |
R4-2204969 |
Further discussion on SRS antenna switching for TxD |
vivo |
R4-2205223 |
Discussion on SRS sharing and antenna switching |
ZTE Wistron Telecom AB |
R4-2205224 |
Draft CR on SRS IL for NR TxD |
ZTE Wistron Telecom AB |
R4-2205576 |
On SRS IL for TxD |
Huawei, HiSilicon |
R4-2206518 |
Draft CR on SRS IL for NR TxD |
ZTE Wistron Telecom AB |
10.7.3.2 |
ULFPTx related |
|
R4-2204617 |
Single-antenna fallback for TxD and UL-MIMO (including ULFPTx) |
Ericsson |
R4-2204618 |
TxD and UL-MIMO requirements for single-port antenna transmission |
Ericsson |
R4-2204828 |
Draft R17 CR on UL MIMO falllback to TxD |
OPPO |
R4-2204835 |
R17 FR1 TxD and ULFPTx fallback |
OPPO |
R4-2204970 |
Discussion on ULFPTx with TxD |
vivo |
R4-2205225 |
ULFPTx requirements for fallback and TxD |
ZTE Wistron Telecom AB |
R4-2205577 |
On ULFPTx and applicable MPR requirements for different PA configurations |
Huawei, HiSilicon |
R4-2205884 |
TxD and ULFPTx requirements |
Qualcomm Incorporated |
R4-2205887 |
Further discussion on transparent TxD – ULFPTx related |
Samsung |
R4-2206519 |
TxD and UL-MIMO requirements for single-port antenna transmission |
Ericsson |
10.8.1 |
General |
|
R4-2206846 |
LS on release independent for Rel-17 FR1 HST RRM enhancement |
CMCC |
10.8.2 |
RRM core requirements |
|
R4-2203710 |
On NR FR1 HST RRM Requirements |
Qualcomm, Inc. |
R4-2206754 |
Email discussion summary for [102-e][211] NR_HST_FR1_enh_RRM_1 |
Moderator (CMCC) |
R4-2206845 |
WF on RRM for FR1 HST |
CMCC |
R4-2207052 |
Email discussion summary for [102-e][211] NR_HST_FR1_enh_RRM_1 |
Moderator (CMCC) |
R4-2207116 |
Big CR: RRM requirements for Rel-17 NR FR1 HST enhancements |
CMCC |
10.8.2.1 |
Intra-frequency measurements |
|
R4-2204269 |
Draft CR on enhanced requirements for SCell measurement for Rel-17 FR1 HST requirements |
CMCC |
10.8.2.2 |
Inter-frequency measurements |
|
R4-2204889 |
Correction on inter-frequency measurements for FR1 HST |
Huawei, Hisilicon |
10.8.2.3 |
L1-SINR measurements |
|
R4-2203741 |
On R17 FR1 HST L1-SINR |
Apple |
R4-2203742 |
CR on L1-SINR measurement in FR1 HST |
Apple |
R4-2203897 |
Discussion on L1-SINR measurements for FR1 HST |
CATT |
R4-2204204 |
Discussion on Rel-17 HST in FR1 |
MediaTek (Shenzhen) Inc. |
R4-2204273 |
Further discussion on remaining issues for Rel17 FR1 HST |
OPPO |
R4-2204334 |
Discussion on L1-SINR measurements in R17 FR1 HST |
vivo |
R4-2204713 |
L1-SINR requirements for NR HST in FR1 |
Ericsson |
R4-2204890 |
Discussion on L1-SINR in FR1 HST |
Huawei, Hisilicon |
R4-2205209 |
Further discussion on L1-SINR measurements for Rel-17 FR1 HST CA |
Nokia, Nokia Shanghai Bell |
10.8.2.4 |
Others |
|
R4-2203743 |
On remaining issues for R17 FR1 HST |
Apple |
R4-2204260 |
Discussion on general requirements for FR1 HST RRM |
CMCC |
R4-2204714 |
Other RRM requirements for NR HST in FR1 |
Ericsson |
R4-2204891 |
Discussion on remaining issues in FR1 HST |
Huawei, Hisilicon |
10.8.3 |
UE demodulation requirements (38.101-4) |
|
R4-2207196 |
Big CR to 38.101-4: Introduction of FR1 HST demodulation requirements |
CMCC |
R4-2207232 |
Draft big CR for 38.101-4: FR2 HST |
Samsung |
10.8.3.1 |
General |
|
R4-2205080 |
Summary for FR1 HST demodulation results |
Ericsson |
R4-2207159 |
Email discussion summary for [102-e][319] NR_HST_FR1_Demod |
Moderator (CMCC) |
R4-2207192 |
draftCR to TS 38.101-4: HST-SFN CA requirements for 2Rx |
Intel |
R4-2207194 |
WF on FR1 HST demodulation |
CMCC |
R4-2207195 |
LS on release independent for FR1 HST demodulation |
CMCC |
R4-2207432 |
Email discussion summary for [102-e][319] NR_HST_FR1_Demod |
Moderator (CMCC) |
10.8.3.2 |
PDSCH requirements for CA scenarios |
|
R4-2203762 |
Discussion on PDSCH CA Requirements in HST |
Apple |
R4-2203763 |
Draft CR on HST DPS CA requirements for 4Rx |
Apple |
R4-2204253 |
Draft CR on PDSCH requirements for HST-SFN CA requirements for 4Rx |
CMCC |
R4-2204259 |
Discussion on FR1 HST UE demodulation for CA scenario |
CMCC |
R4-2204384 |
Discussion on HST FR1 CA PDSCH performance requirements |
Intel Corporation |
R4-2204385 |
draftCR to TS 38.101-4: HST-SFN CA requirements for 2Rx |
Intel Corporation |
R4-2204430 |
Discussion on PDSCH requirements for FR1 HST CA scenarios |
ZTE Corporation |
R4-2205081 |
PDSCH demodulation requirements for CA with HST-SFN scenario |
Ericsson |
R4-2205082 |
draft CR: FRC for CA PDSCH demodulation requirements for HST |
Ericsson |
R4-2205752 |
Discussion on PDSCH CA scenarios for NR UE HST FR1 performance requirements |
Huawei,HiSilicon |
R4-2205753 |
Draft CR on HST FR1 DPS CA requirements for 2Rx (38.101-4) |
Huawei,HiSilicon |
R4-2206090 |
Views on FR1 HST PDSCH CA Tests |
Qualcomm Incorporated |
R4-2206110 |
Draft CR on Applicability Rules for FR1 HST CA requirements |
Qualcomm Incorporated |
R4-2207190 |
Draft CR on HST DPS CA requirements for 4Rx |
Apple |
R4-2207191 |
Draft CR on PDSCH requirements for HST-SFN CA requirements for 4Rx |
CMCC |
R4-2207193 |
Draft CR on HST FR1 DPS CA requirements for 2Rx (38.101-4) |
Huawei,HiSilicon |
R4-2207234 |
Draft CR on Applicability Rules for FR1 HST CA requirements |
Qualcomm Incorporated |
10.9.1 |
General |
|
R4-2206594 |
TR 38.854, NR support for high speed train scenario in frequency range 2 (FR2) |
Nokia, Nokia Shanghai Bell, Samsung |
10.9.2 |
UE RF core requirements |
|
R4-2203712 |
On FR2 HST RF Requirements |
Qualcomm, Inc. |
R4-2205888 |
Remaining Issues on RF requirement for FR2 PC6 UE |
Samsung |
R4-2205889 |
CR to introduce UE RF requirement for FR2 PC 6 UE |
Samsung |
R4-2206329 |
Email discussion summary for [102-e][129] NR_HST_FR2 |
Moderator (Samsung) |
R4-2206429 |
Email discussion summary for [102-e][129] NR_HST_FR2 |
Moderator (Samsung) |
R4-2206520 |
WF on remaining issues for FR2 PC6 for HST Scenarios |
Samsung |
R4-2206521 |
CR to introduce UE RF requirement for FR2 PC 6 UE |
Samsung |
10.9.2.1.2 |
Spherical coverage requirements |
|
R4-2204431 |
Discussion on Spherical coverage requirements for HST_FR2 |
ZTE Corporation |
R4-2205211 |
UE spherical coverage requirement for FR2 HST |
Nokia, Nokia Shanghai Bell |
10.9.3 |
RRM core requirements |
|
R4-2203711 |
On NR FR2 HST RRM Requirements |
Qualcomm, Inc. |
R4-2206848 |
WF on FR2 HST RRM (part 1) |
Nokia, Nokia Shanghai Bell |
R4-2206860 |
TP to TR 38.854 on RA-based UL Timing Adjustment for FR2 HST |
Huawei, Hisilicon |
10.9.3.1 |
General |
|
R4-2203714 |
TP to TR 38.854 on the Number of Rx beams |
Qualcomm, Inc. |
R4-2203898 |
Discussion on general issues for FR2 HST |
CATT |
R4-2204715 |
General requirements for HST FR2 |
Ericsson |
R4-2204720 |
LS on network signalling for Rel-17 NR HST RRM |
Ericsson |
R4-2204721 |
draft CR On RRC_CONNECTED state mobility for HST FR2 RRM |
Ericsson |
R4-2205008 |
General RRM requirements for HST FR2 |
ZTE Corporation |
R4-2205895 |
Discussion on capability and feature list for FR2 HST UE |
Samsung |
R4-2205896 |
TP to TR 38.854 – beam coverage for FR2 HST |
Nokia, Nokia Shanghai Bell |
R4-2205900 |
Link simulation assumptions for L1 and L3 measurement accuracy for FR2 HST scenarios |
Nokia, Nokia Shanghai Bell |
R4-2206008 |
Discussion on applicability of enhanced requirements for HST in FR2 |
Intel Corporation |
R4-2206016 |
Big CR to TS 38.133 on HST FR2 RRM Core Requirements |
Nokia, Nokia Shanghai Bell |
R4-2206755 |
Email discussion summary for [102-e][212] NR_HST_FR2_RRM_1 |
Moderator (Intel) |
R4-2206849 |
TP to TR 38.854 on the Number of Rx beams |
Qualcomm, Inc. |
R4-2206850 |
draft CR On RRC_CONNECTED state mobility for HST FR2 RRM |
Ericsson |
R4-2207053 |
Email discussion summary for [102-e][212] NR_HST_FR2_RRM_1 |
Moderator (Intel) |
10.9.3.2 |
RRC Idle/Inactive and connected state mobility requirements |
|
R4-2204254 |
Discussion on mobility requirements for FR2 HST |
CMCC |
R4-2204489 |
Draft CR for Cell re-selection for HST FR2 |
ZTE Corporation |
R4-2204629 |
CR to TS 38.133: intra-frequency measurements without gaps for for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
R4-2204716 |
RRC Idle/Inactive and connected state mobility requirements |
Ericsson |
R4-2204892 |
Discussion on RRC Idle/Inactive and connected state mobility requirements for HST in FR2 |
Huawei, Hisilicon |
R4-2205898 |
On remaining RRM measurement open issues for FR2 HST |
Nokia, Nokia Shanghai Bell |
R4-2205960 |
TP to TR 38.854 on Legacy RRM Requirement Mobility Performance in HST FR2 Deployment Scenarios |
Nokia, Nokia Shanghai Bell |
R4-2206851 |
Draft CR for Cell re-selection for HST FR2 |
ZTE Corporation |
R4-2206853 |
CR to TS 38.133: intra-frequency measurements without gaps for for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
10.9.3.3 |
Timing requirements |
|
R4-2203713 |
Draft CR to introduce one shot large UL timing adjustment for FR2 HST UE |
Qualcomm, Inc. |
R4-2203754 |
Discussion on timing requirement for FR2 HST |
Apple |
R4-2203899 |
Discussion on timing requirement for FR2 HST |
CATT |
R4-2204631 |
CR to TS 38.133: Tq timing adjustment requirements for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
R4-2204719 |
On Timing requirements for HST FR2 |
Ericsson |
R4-2205890 |
Remaining Issues on Timing Requirements for FR2 HST |
Samsung |
R4-2205891 |
TP to TR 38.854 on RA-based UL Timing Adjustment for FR2 HST |
Samsung |
R4-2205892 |
Draft CR to introduce one shot large UL timing adjustment for FR2 HST UE |
Samsung |
R4-2205959 |
On HST FR2 UL Timing Adjustment |
Nokia, Nokia Shanghai Bell |
R4-2206756 |
Email discussion summary for [102-e][213] NR_HST_FR2_RRM_2 |
Moderator (Samsung) |
R4-2206858 |
CR to TS 38.133: Tq timing adjustment requirements for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
R4-2207054 |
Email discussion summary for [102-e][213] NR_HST_FR2_RRM_2 |
Moderator (Samsung) |
R4-2207107 |
CR to TS 38.133: Tq timing adjustment requirements for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
10.9.3.4 |
Signalling characteristics requirements |
|
R4-2203755 |
Discussion on signalling characteristics requirements |
Apple |
R4-2203900 |
Discussion on TCI switching delay for FR2 HST |
CATT |
R4-2203901 |
Draft CR on RLM/BFD requirement for FR2 HST |
CATT |
R4-2204718 |
Signalling characteristics requirements for HST FR2 |
Ericsson |
R4-2204893 |
Discussion on signaling characteristics requirements for high speed train scenario in FR2 |
Huawei, Hisilicon |
R4-2205009 |
Discussion on Signaling characteristics for HST FR2 |
ZTE Corporation |
R4-2205893 |
Remaining Issues on signaling characteristics requirements for FR2 HST |
Samsung |
R4-2205894 |
Draft CR to introduce active TCI state switching delay requirement for FR2 HST UE |
Samsung |
R4-2206855 |
Draft CR on RLM/BFD requirement for FR2 HST |
CATT |
R4-2206856 |
Draft CR to introduce active TCI state switching delay requirement for FR2 HST UE |
Samsung |
R4-2206857 |
Draft CR to introduce one shot large UL timing adjustment for FR2 HST UE |
Qualcomm Incorporated |
R4-2206859 |
Draft CR to introduce one shot large UL timing adjustment for FR2 HST UE |
Samsung |
10.9.3.5 |
Measurement procedure requirements |
|
R4-2203756 |
Discussion on measurement procedure requirement for FR2 HST |
Apple |
R4-2203902 |
Discussion on measurement procedure requirements for FR2 HST |
CATT |
R4-2204490 |
Draft CR for L1-RSRP measurements for Reporting for HST FR2 |
ZTE Corporation |
R4-2204717 |
Measurement procedure requirements for HST FR2 |
Ericsson |
R4-2204894 |
Discussion on RRM requirements for high speed train scenario in FR2 |
Huawei, Hisilicon |
R4-2204895 |
Scheduling restriction for L1-SINR for FR2 HST |
Huawei, Hisilicon |
R4-2205961 |
TP to TR 38.854 on Analysis of Mobility Performance in HST FR2 Deployment Scenarios |
Nokia, Nokia Shanghai Bell |
R4-2206852 |
Draft CR for L1-RSRP measurements for Reporting for HST FR2 |
ZTE Corporation |
R4-2206854 |
Scheduling restriction for L1-SINR for FR2 HST |
Huawei, Hisilicon |
10.9.4.1 |
General |
|
R4-2205754 |
Draft CR on minimum requirements for PDSCH HST-DPS (38.101-4) |
Huawei,HiSilicon |
R4-2206077 |
draft CR for FR2 HST - High speed Train Scenarios (B.3.4) |
Qualcomm Incorporated |
R4-2207160 |
Email discussion summary for [102-e][320] NR_HST_FR2_Demod_Part1 |
Moderator (Samsung) |
R4-2207226 |
Draft CR on minimum requirements for PDSCH HST-DPS (38.101-4) |
Huawei,HiSilicon |
R4-2207227 |
draft CR for FR2 HST – High speed Train Scenarios (B.3.4) |
Qualcomm Incorporated |
R4-2207230 |
WF on UE demodulation requirement for FR2 HST |
Samsung |
R4-2207433 |
Email discussion summary for [102-e][320] NR_HST_FR2_Demod_Part1 |
Moderator (Samsung) |
10.9.4.2 |
UE demodulation requirements |
|
R4-2203541 |
Simulation results summary for Rel-17 FR2 HST UE demod |
Samsung |
R4-2204255 |
Discussion on UE demodulation for FR2 HST |
CMCC |
R4-2204387 |
Views on FR2 HST PDSCH performance requirements |
Intel Corporation |
R4-2204388 |
DraftCR to TS 38.101-4: Applicability rules for HST FR2 PDSCH requirements |
Intel Corporation |
R4-2205084 |
draft CR: FRC for PDSCH demodulation requirement for FR2 HST |
Ericsson |
R4-2206073 |
Addressing open issues on FR2 HST UE Demodulation |
Qualcomm Incorporated |
10.9.4.2.1 |
PDSCH requirements under Uni-directional scenario |
|
R4-2203543 |
Discussion and simulation results of PDSCH requirement with Uni-directional scenario for Rel-17 FR2 HST |
Samsung |
R4-2205083 |
PDSCH demodulation requirements for HST FR2 |
Ericsson |
R4-2205756 |
Discussion on UE demodulation requirements for FR2 HST Ui-directional |
Huawei,HiSilicon |
10.9.4.2.2 |
PDSCH requirements under Bi-directional scenario |
|
R4-2203544 |
Discussion and simulation results of PDSCH requirement with Bi-directional scenario for Rel-17 FR2 HST |
Samsung |
R4-2204432 |
PDSCH requirements under Bi-directional scenario |
ZTE Corporation |
R4-2205757 |
Discussion on UE demodulation requirements for FR2 HST Bi-directional |
Huawei,HiSilicon |
10.9.4.3 |
BS demodulation requirements |
|
R4-2203542 |
Simulation results summary for Rel-17 FR2 HST BS demod |
Samsung |
R4-2205034 |
On the OTA test setup CR for 38.141-2 |
Ericsson |
R4-2205755 |
Draft CR on HST FR2 BS applicability rule (38.141-2) |
Huawei,HiSilicon |
R4-2207161 |
Email discussion summary for [102-e][321] NR_HST_FR2_Demod_Part2 |
Moderator (Nokia) |
R4-2207235 |
WF on BS demodulation requirement for FR2 HST |
Nokia |
R4-2207434 |
Email discussion summary for [102-e][321] NR_HST_FR2_Demod_Part2 |
Moderator (Nokia) |
10.9.4.3.1 |
PUSCH requirements |
|
R4-2203545 |
Discussion and simulation results of PUSCH requirement for Rel-17 FR2 HST |
Samsung |
R4-2203971 |
Discussion on PUSCH demodulation requirements for FR2 HST |
CATT |
R4-2203972 |
Simulation results for PUSCH demodulation requirements for FR2 HST |
CATT |
R4-2204389 |
DraftCR to TS 38.104: FRC for HST FR2 PUSCH performance requirements |
Intel Corporation |
R4-2204390 |
DraftCR to TS 38.104: HST FR2 PUSCH performance requirements |
Intel Corporation |
R4-2204391 |
DraftCR to TS 38.141-2: FRC for HST FR2 PUSCH performance requirements |
Intel Corporation |
R4-2204392 |
HST FR2 PUSCH simulation results |
Intel Corporation |
R4-2205023 |
HST PUSCH requirements |
Ericsson |
R4-2205033 |
Draft CR on introduction of FR2 HST test procedure for PUSCH |
Ericsson |
R4-2205758 |
Discussion on PUSCH demodulation requirements for FR2 HST |
Huawei,HiSilicon |
R4-2205965 |
On HST FR2 PUSCH Demodulation Requirements |
Nokia, Nokia Shanghai Bell |
10.9.4.3.2 |
PUSCH with UL timing adjustment requirements |
|
R4-2203546 |
Simulation results of UL timing adjustment requirement for Rel-17 FR2 HST |
Samsung |
R4-2203973 |
Simulation results for UL timing adjustment demodulation requirements for FR2 HST |
CATT |
R4-2204393 |
HST FR2 UL TA simulation results |
Intel Corporation |
R4-2205759 |
Simulation results on PUSCH with UL timing adjustment requirements for FR2 HST |
Huawei,HiSilicon |
R4-2205963 |
HST FR2 PUSCH UL TA Impairment Simulation Results |
Nokia, Nokia Shanghai Bell |
10.9.4.3.3 |
PRACH requirements |
|
R4-2203547 |
Simulation results of PRACH requirement for Rel-17 FR2 HST |
Samsung |
R4-2203974 |
Simulation results for PRACH demodulation requirements for FR2 HST |
CATT |
R4-2204394 |
HST FR2 PRACH simulation results |
Intel Corporation |
R4-2205760 |
Simulation results on PRACH demodulation requirements for FR2 HST |
Huawei,HiSilicon |
R4-2205761 |
Draft CR on PRACH minimum requirements for high speed train (38.104) |
Huawei,HiSilicon |
R4-2205762 |
Draft CR on PRACH test requirement for high speed train (38.141-2) |
Huawei,HiSilicon |
R4-2205964 |
HST FR2 PRACH Impairment Simulation Results |
Nokia, Nokia Shanghai Bell |
R4-2207236 |
Draft CR on PRACH minimum requirements for high speed train (38.104) |
Huawei,HiSilicon |
R4-2207237 |
Draft CR on PRACH test requirement for high speed train (38.141-2) |
Huawei,HiSilicon |
10.10.1 |
General |
|
R4-2207117 |
Big CR: RRM requirements for Rel-17 NR FeRRM (TS 38.133) |
Apple |
R4-2207118 |
Big CR: RRM requirements for Rel-17 NR FeRRM (TS 36.133) |
Apple |
10.10.2.1 |
SRS antenna port switching |
|
R4-2203717 |
On SRS antenna switching |
Qualcomm, Inc. |
R4-2203783 |
Discussion on SRS antenna port switching |
Apple |
R4-2203921 |
Further discussion on SRS antenna port switching |
CATT |
R4-2203922 |
Interruption requirement to LTE serving cell, and impacts to other LTE RRM requirement |
CATT |
R4-2204242 |
Further discussion on RRM requirements for SRS antenna switching |
Xiaomi |
R4-2204265 |
Discussion on SRS antenna port switching |
CMCC |
R4-2204274 |
RRM requirements for SRS ant port switch |
OPPO |
R4-2204314 |
Discussion on interruption due to SRS antenna port switching |
LG Electronics Inc. |
R4-2204335 |
Discussion on RRM requirements for SRS antenna port switching |
vivo |
R4-2204362 |
Discussion on SRS antenna port switching |
MediaTek Inc. |
R4-2204399 |
Discussion on SRS antenna port switching |
Intel Corporation |
R4-2204704 |
Interruption requirements at SRS antenna port switching |
Nokia, Nokia Shanghai Bell |
R4-2204705 |
38.133 draftCR on introduction of SRS antenna switching |
Nokia, Nokia Shanghai Bell |
R4-2204869 |
Discussion on requirements for SRS antenna switching |
Huawei, Hisilicon |
R4-2205836 |
RRM requirements for SRS antenna port switching |
Ericsson |
R4-2205837 |
Draft CR on Interruption requirement to NR serving cell, and impacts to other NR RRM requirement (if applicable) |
Ericsson |
R4-2206757 |
Email discussion summary for [102-e][214] NR_RRM_enh2_1 |
Moderator (Apple) |
R4-2206861 |
WF on further RRM enhancement for NR and MR-DC - SRS antenna port switching |
Apple |
R4-2206862 |
Interruption requirement to LTE serving cell, and impacts to other LTE RRM requirement |
CATT |
R4-2206863 |
Draft CR on Interruption requirement to NR serving cell, and impacts to other NR RRM requirement (if applicable) |
Ericsson |
R4-2207055 |
Email discussion summary for [102-e][214] NR_RRM_enh2_1 |
Moderator (Apple) |
10.10.2.2 |
HO with PSCell |
|
R4-2203784 |
Discussion on RRM requirement for handover with PSCell |
Apple |
R4-2203785 |
Draft CR on HO with PSCell for NR SA to EN-DC_R17 |
Apple |
R4-2203866 |
RRM requirements for HO with PSCell |
Qualcomm Incorporated |
R4-2203923 |
Further discussion on HO with PSCell |
CATT |
R4-2204162 |
Discussion on RRM requirements for HO with PSCell |
ZTE Corporation |
R4-2204231 |
Further discussion on RRM requirements for handover with PSCell |
Xiaomi |
R4-2204256 |
Discussion on HO with PSCell |
CMCC |
R4-2204275 |
RRM requirements for HO with PSCell |
OPPO |
R4-2204336 |
Discussion on RRM requirements for HO with PSCell |
vivo |
R4-2204400 |
Discussion on HO with PSCell |
Intel Corporation |
R4-2204870 |
Discussion on requirements for HO with PSCell |
Huawei, Hisilicon |
R4-2204871 |
Draft CR on requirements for HO with PSCell from EN-DC to EN-DC |
Huawei, Hisilicon |
R4-2205838 |
RRM requirements for handover with PSCell |
Ericsson |
R4-2205839 |
Drfat CR on HO with PSCell requirements for NE DC to NE-DC |
Ericsson |
R4-2205863 |
Discussion on HO with PSCell |
MediaTek Inc. |
R4-2205876 |
discussion on HO with PSCell |
Nokia, Nokia Shanghai Bell |
R4-2205877 |
dratCR on HO with PSCell for NR-DC to NR-DC |
Nokia, Nokia Shanghai Bell |
R4-2206758 |
Email discussion summary for [102-e][215] NR_RRM_enh2_2 |
Moderator (Vivo) |
R4-2206814 |
Draft CR on radio link monitoring test cases |
CATT |
R4-2206864 |
WF on further RRM enhancement for NR and MR-DC – HO with PSCell |
Vivo |
R4-2206865 |
Draft CR on HO with PSCell for NR SA to EN-DC_R17 |
Apple |
R4-2206866 |
Draft CR on requirements for HO with PSCell from EN-DC to EN-DC |
Huawei, Hisilicon |
R4-2206867 |
Drfat CR on HO with PSCell requirements for NE DC to NE-DC |
Ericsson |
R4-2206868 |
dratCR on HO with PSCell for NR-DC to NR-DC |
Nokia, Nokia Shanghai Bell |
R4-2207056 |
Email discussion summary for [102-e][215] NR_RRM_enh2_2 |
Moderator (Vivo) |
R4-2207106 |
WF on further RRM enhancement for NR and MR-DC – HO with PSCell |
Vivo |
10.10.2.3 |
PUCCH SCell activation/deactivation |
|
R4-2203786 |
Discussion on PUCCH SCell activation and deactivation |
Apple |
R4-2203852 |
PUCCH SCell activation and deactivation |
Qualcomm Incorporated |
R4-2203924 |
Further discussion on PUCCH SCell activation_deactivation |
CATT |
R4-2203925 |
PUCCH Scell activation delay requirements with multiple Scell |
CATT |
R4-2204232 |
Further discussion on SCell activation and deactication requirements for PUCCH SCell |
Xiaomi |
R4-2204264 |
Discussion on PUCCH SCell activation/deactivation |
CMCC |
R4-2204276 |
RRM requirements for PUCCH SCell Activation/Deactivation |
OPPO |
R4-2204363 |
Discussion on PUCCH SCell activation and deactivation |
MediaTek Inc. |
R4-2204364 |
Draft CR for PUCCH SCell deactivation delay requirements in TS 38.133 |
MediaTek Inc. |
R4-2204401 |
Discussion on PUCCH SCell activation |
Intel Corporation |
R4-2204688 |
Discussions on PUCCH SCell Activation/Deactivation delay requirements |
NTT DOCOMO, INC. |
R4-2204702 |
Discussion on the activation delay for deactivated PUCCH SCell |
Nokia, Nokia Shanghai Bell |
R4-2204703 |
38.133 draft CR on PUCCH SCell activation delay requirements |
Nokia, Nokia Shanghai Bell |
R4-2204872 |
Discussion on requirements for PUCCH SCell activation |
Huawei, Hisilicon |
R4-2204873 |
Draft CR on requirements for interruption requirements to NR serving Cell for PUCCH SCell activation |
Huawei, Hisilicon |
R4-2205840 |
RRM requirements for SCell activation/deactivation with PUCCH |
Ericsson |
R4-2205841 |
Draft CR on Interruption requirements to LTE serving cell |
Ericsson |
R4-2206759 |
Email discussion summary for [102-e][216] NR_RRM_enh2_3 |
Moderator (CATT) |
R4-2206869 |
WF on further RRM enhancement for NR and MR-DC – PUCCH SCell activation/deactivation requirements |
CATT |
R4-2206870 |
PUCCH Scell activation delay requirements with multiple Scell |
CATT |
R4-2206871 |
38.133 draft CR on PUCCH SCell activation delay requirements |
Nokia, Nokia Shanghai Bell |
R4-2206872 |
Draft CR on requirements for interruption requirements to NR serving Cell for PUCCH SCell activation |
Huawei, Hisilicon |
R4-2206873 |
Draft CR on Interruption requirements to LTE serving cell |
Ericsson |
R4-2207035 |
Draft CR on intra-frequency measurement requirements for Rel-17 NB-IoT |
Huawei, Hisilicon |
R4-2207057 |
Email discussion summary for [102-e][216] NR_RRM_enh2_3 |
Moderator (CATT) |
10.11.1 |
General |
|
R4-2207119 |
Big CR: RRM requirements for Rel-17 NR MG enhancements |
Intel Corporation, MediaTek |
R4-2207543 |
Big CR: RRM requirements for Rel-17 NR MG enhancements |
Intel Corporation, MediaTek |
10.11.2.1 |
Pre-configured MG pattern(s) |
|
R4-2203735 |
On Pre-MG pattern |
Apple |
R4-2203736 |
CR on Pre-MG activation/deactivation delay |
Apple |
R4-2203877 |
Further discussion on pre-configured MG pattern |
CATT |
R4-2203878 |
Draft CR on measurement delay requirements with Pre-MG |
CATT |
R4-2204055 |
Discussion on pre-configured gap |
MediaTek inc. |
R4-2204056 |
Draft CR on 38.133 for L1 measurement impact of preconfigured gap |
MediaTek inc. |
R4-2204233 |
Further discussion on pre-configured MG pattern for NR |
Xiaomi |
R4-2204263 |
Discussion on pre-configured MG pattern(s) |
CMCC |
R4-2204277 |
On pre-configured MG pattern(s) for NR_MG_enh |
OPPO |
R4-2204319 |
Further consideration on remaining issues on pre-configured MG patterns |
vivo |
R4-2204404 |
Discussion on pre-configured measurement gap |
Intel Corporation |
R4-2204467 |
On pre-configured measurement gaps |
Qualcomm Incorporated |
R4-2205010 |
Views on pre-configured MG patterns |
ZTE Corporation |
R4-2205368 |
Discussion on pre-configured MG |
Huawei, HiSilicon |
R4-2205369 |
CR on pre-MG applicability |
Huawei, HiSilicon |
R4-2205936 |
Discussion on Pre-configured MG patterns |
Nokia, Nokia Shanghai Bell |
R4-2206017 |
Further analysis of pre-configured measurement gap pattern |
Ericsson |
R4-2206018 |
Updates to rules for pre-MG status change in TS 38.133 |
Ericsson |
R4-2206761 |
Email discussion summary for [102-e][218] NR_MG_enh_2 |
Moderator (Intel) |
R4-2206883 |
WF on R17 NR MG enhancements – Pre-configured MG |
Intel Corporation |
R4-2206884 |
CR on Pre-MG activation/deactivation delay |
Apple |
R4-2206885 |
Draft CR on measurement delay requirements with Pre-MG |
CATT |
R4-2206887 |
CR on pre-MG applicability |
Huawei, HiSilicon |
R4-2207024 |
CR on requirements for UE Rx-Tx measurement for PDC |
Huawei, HiSilicon |
R4-2207059 |
Email discussion summary for [102-e][218] NR_MG_enh_2 |
Moderator (Intel) |
10.11.2.2 |
Multiple concurrent and independent MG patterns |
|
R4-2203737 |
On multiple concurrent and independent MG patterns |
Apple |
R4-2203738 |
CR on CSSF for concurrent gaps |
Apple |
R4-2203879 |
Further discussion on multiple concurrent and independent MG patterns |
CATT |
R4-2203880 |
Draft CR on measurement delay requirements for concurrent MG patterns |
CATT |
R4-2204057 |
Discussion on concurrent gaps |
MediaTek inc. |
R4-2204058 |
Draft CR on 38.133 for L1 measurement impact of concurrent gaps |
MediaTek inc. |
R4-2204150 |
Discussion on multiple concurrent and independent MG patterns |
LG Electronics |
R4-2204234 |
Further discussion on multiple concurrent and independent MG patterns for NR |
Xiaomi |
R4-2204235 |
DraftCR on inter-frequency measurement delay requirements with concurrent gaps |
Xiaomi |
R4-2204257 |
Discussion on multiple concurrent and independent MG patterns |
CMCC |
R4-2204278 |
On multiple concurrent and independent MG patterns for NR_MG_enh |
OPPO |
R4-2204279 |
Draft CR to 38133 on CSI-RS based L3 measurement requirements with concurrent gap |
OPPO |
R4-2204320 |
Further consideration on remaining issues on multiple concurrent and independent MG patterns |
vivo |
R4-2204405 |
Discussion on multiple and independent concurrent measurement gaps in NR |
Intel Corporation |
R4-2204411 |
DraftCR to TS 38.133: Positioning measurement requirements due to concurrent gap in NR |
Intel Corporation |
R4-2204468 |
On multiple concurrent measurement gaps |
Qualcomm Incorporated |
R4-2205011 |
Views on multiple concurrent and independent MGs |
ZTE Corporation |
R4-2205370 |
Discussion on multiple concurrent MGs |
Huawei, HiSilicon |
R4-2205371 |
CR on collision handling for concurrent MGs |
Huawei, HiSilicon |
R4-2205516 |
Discussion on Multiple concurrent MG patterns |
Ericsson |
R4-2205517 |
draftCR on concurrent gaps(9.1.2B) |
Ericsson |
R4-2205651 |
Concurrent measurement gap enhancements |
Nokia, Nokia Shanghai Bell |
R4-2205652 |
Draft CR: Corrections to RRM requirements Rel-17 NR MG enhancements |
Nokia, Nokia Shanghai Bell |
R4-2206760 |
Email discussion summary for [102-e][217] NR_MG_enh_1 |
Moderator (MediaTek) |
R4-2206785 |
LS on collision handling of concurrent MGs |
MediaTek inc. |
R4-2206786 |
LS on R17 NR MG enhancements – Pre-configured MG |
Huawei, Intel |
R4-2206788 |
LS on collision handling of concurrent MGs |
MediaTek inc. |
R4-2206789 |
LS on R17 NR MG enhancements – Pre-configured MG |
Huawei, Intel |
R4-2206830 |
CR on CSI-RS measurement requirements R16 |
Huawei, HiSilicon |
R4-2206874 |
WF on R17 NR MG enhancements – multiple concurrent MGs |
MediaTek inc. |
R4-2206875 |
Draft CR on measurement delay requirements for concurrent MG patterns |
CATT |
R4-2206876 |
Draft CR on 38.133 for L1 measurement impact of concurrent gaps |
MediaTek inc. |
R4-2206877 |
DraftCR on inter-frequency measurement delay requirements with concurrent gaps |
Ericsson |
R4-2206878 |
Draft CR to 38133 on CSI-RS based L3 measurement requirements with concurrent gap |
OPPO |
R4-2206879 |
DraftCR to TS 38.133: Positioning measurement requirements due to concurrent gap in NR |
Intel Corporation |
R4-2206880 |
CR on collision handling for concurrent MGs |
Huawei, HiSilicon |
R4-2206881 |
draftCR on concurrent gaps(9.1.2B) |
Ericsson |
R4-2206882 |
Draft CR: Corrections to RRM requirements Rel-17 NR MG enhancements |
Nokia, Nokia Shanghai Bell |
R4-2206929 |
draftCR on cell reselection in Idle mode for FR2-2 CCA |
Ericsson |
R4-2207058 |
Email discussion summary for [102-e][217] NR_MG_enh_1 |
Moderator (MediaTek) |
R4-2207084 |
CR on CSSF for concurrent gaps |
Apple |
10.11.2.3 |
Network Controlled Small Gap |
|
R4-2203715 |
On Network Controlled Small Gap RRM Requirement |
Qualcomm, Inc. |
R4-2203716 |
CR: NCSG scheduling restriction |
Qualcomm, Inc. |
R4-2203739 |
On network controlled small gap |
Apple |
R4-2203740 |
CR on NCSG |
Apple |
R4-2203881 |
Further discussion on Network Controlled Small Gap (NCSG) |
CATT |
R4-2203882 |
Draft CR on measurement delay requirements with NCSG |
CATT |
R4-2204059 |
Discussion on NCSG |
MediaTek inc. |
R4-2204060 |
Draft CR on 38.133 for L1 measurement impact of NCSG |
MediaTek inc. |
R4-2204258 |
Further discussion on Network Controlled Small Gap |
CMCC |
R4-2204293 |
Discussion on NCSG for NR_MG_enh |
OPPO |
R4-2204294 |
Draft CR to UE behaviour to group the frequency layers with NCSG |
OPPO |
R4-2204406 |
Discussion on NCSG in NR |
Intel Corporation |
R4-2205012 |
Views on NCSG |
ZTE Corporation |
R4-2205372 |
Discussion on NCSG |
Huawei, HiSilicon |
R4-2205373 |
CR on use cases and CSSF for NCSG |
Huawei, HiSilicon |
R4-2205937 |
Discussion on Network Controlled Small Gaps for NR |
Nokia, Nokia Shanghai Bell |
R4-2206019 |
Further analysis of network controlled small gap |
Ericsson |
R4-2206020 |
Updates to NCSG patterns in TS 38.133 |
Ericsson |
R4-2206762 |
Email discussion summary for [102-e][219] NR_MG_enh_3 |
Moderator (Apple) |
R4-2206886 |
Draft CR on 38.133 for L1 measurement impact of preconfigured gap |
MediaTek inc. |
R4-2206889 |
WF on NCSG |
Apple |
R4-2206890 |
LS on R17 MG enhancement - NCSG |
Apple |
R4-2206892 |
CR: NCSG scheduling restriction |
Qualcomm, Inc. |
R4-2206893 |
CR on NCSG |
Apple |
R4-2206894 |
Draft CR on measurement delay requirements with NCSG |
CATT |
R4-2206895 |
Draft CR on 38.133 for L1 measurement impact of NCSG |
MediaTek inc. |
R4-2206896 |
Draft CR to UE behaviour to group the frequency layers with NCSG |
OPPO |
R4-2206897 |
CR on use cases and CSSF for NCSG |
Huawei, HiSilicon |
R4-2206898 |
Updates to NCSG patterns in TS 38.133 |
Ericsson |
R4-2207060 |
Email discussion summary for [102-e][219] NR_MG_enh_3 |
Moderator (Apple) |
10.12.1 |
General |
|
R4-2204375 |
Discussion on UE feature list and capability signalling |
Intel Corporation |
R4-2205788 |
Discussions on UE feature list for MMSE-IRC receiver |
Huawei,HiSilicon |
R4-2207162 |
Email discussion summary for [102-e][322] NR_perf_enh2_Demod_Part1 |
Moderator (China Telecom) |
R4-2207239 |
WF on general part and 15kHz NR SCS scenario for CRS-IM receiver |
China Telecom |
R4-2207240 |
WF on 30 kHz NR SCS scenario for CRS-IM receiver |
CMCC |
R4-2207242 |
WF on general and PDSCH demodulation requirements for inter-cell interference MMSE-IRC |
Intel Corporation |
R4-2207243 |
WF on CSI requirements for inter-cell interference MMSE-IRC |
Ericsson |
R4-2207244 |
WF on MMSE-IRC receiver for intra-cell inter-user interference |
Huawei |
R4-2207435 |
Email discussion summary for [102-e][322] NR_perf_enh2_Demod_Part1 |
Moderator (China Telecom) |
10.12.2.1.1 |
PDSCH requirements |
|
R4-2203764 |
Discussion on PDSCH requirements in intercell interference scenarios |
Apple |
R4-2203765 |
Draft CR on PDSCH demod requirements in ICI-FDD |
Apple |
R4-2204376 |
Discussion on PDSCH demodulation MMSE-IRC requirements for scenario with inter-cell interference |
Intel Corporation |
R4-2204377 |
Summary of PDSCH simulation results for inter-cell interference suppression |
Intel Corporation |
R4-2204488 |
Views on MMSE-IRC receiver for inter-cell interference test |
NTT DOCOMO, INC. |
R4-2204523 |
Draft CR for TS38.101-4 PDSCH TDD demodulation requirements for inter-cell interference MMSE-IRC |
CMCC |
R4-2204524 |
Discussion on R17 demodulation enhancement for inter-cell interference suppressing |
CMCC |
R4-2204830 |
draftCR to TS 38.101-4: NR Interference model for enhanced performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2204832 |
On Intercell PDSCH MMSE-IRC demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2205497 |
On PDSCH requirements for UE MMSE-IRC receiver for inter-cell interference suppression |
China Telecom |
R4-2205502 |
Remaining issues on PDSCH requirement for inter-cell interference |
Ericsson |
R4-2205503 |
Simulation results on PDSCH performance for inter-cell interference |
Ericsson |
R4-2205789 |
Discussion on demodulation requirements for inter-cell MMSE-IRC receiver |
Huawei,HiSilicon |
R4-2205790 |
Simulation results on demodulation requirements for inter-cell MMSE-IRC receiver |
Huawei,HiSilicon |
R4-2205791 |
Draft CR: Introduction of general and applicability section of inter-cell MMSE-IRC receiver in TS 38.101-4 |
Huawei,HiSilicon |
R4-2205901 |
Discussion on the PDSCH requirements for scenarios with inter-cell inter-user interference |
MediaTek inc. |
R4-2206070 |
Views on Inter-cell Interference PDSCH Tests |
Qualcomm Incorporated |
R4-2207245 |
Draft CR on PDSCH demod requirements in ICI-FDD |
Apple |
R4-2207246 |
Draft CR for TS38.101-4 PDSCH TDD demodulation requirements for inter-cell interference MMSE-IRC |
CMCC |
R4-2207250 |
Draft CR for TS38.141-2 Requirements for PUSCH with transform precoding disabled for BS type 1-O |
CMCC |
10.12.2.1.2 |
CQI requirements |
|
R4-2203766 |
Discussion on CSI reporting requirements in intercell interference scenarios |
Apple |
R4-2204378 |
Discussion on CSI MMSE-IRC requirements for scenario with inter-cell interference |
Intel Corporation |
R4-2204831 |
On CQI requirements for intercell interference MMSE-IRC |
Nokia, Nokia Shanghai Bell |
R4-2205498 |
On CSI requirements for UE MMSE-IRC receiver for inter-cell interference suppression |
China Telecom |
R4-2205504 |
Remaining issues on CSI reporting requirements for inter-cell interference |
Ericsson |
R4-2205505 |
Simulation results on CSI reporting for inter-cell interference |
Ericsson |
R4-2205508 |
draftCR on CSI reporting test case(TDD) |
Ericsson |
R4-2205509 |
Summary of simulation results for Inter-cell MMSE-IRC CQI reporting |
Ericsson |
R4-2205792 |
Discussions on remain issues for inter cell MMSE-IRC CQI requirements |
Huawei,HiSilicon |
R4-2205793 |
Simulations results for inter cell MMSE-IRC CQI requirements |
Huawei,HiSilicon |
R4-2205902 |
Discussion on the CQI requirements for scenarios with inter-cell inter-user interference |
MediaTek inc. |
R4-2206086 |
Simulation results for Inter-cell Interference CQI Reporting Tests |
Qualcomm Incorporated |
10.12.2.2 |
MMSE-IRC receiver for intra-cell inter-user interference |
|
R4-2203767 |
Discussion on PDSCH requirements in MU-MIMO scenarios |
Apple |
R4-2203768 |
TP to TR 38.833: MU-MIMO-Receiver structure |
Apple |
R4-2204379 |
Discussion on MMSE-IRC requirements for scenario with intra-cell inter-user interference |
Intel Corporation |
R4-2204380 |
TP to TR 38.833: Link level simulation results for Inter-user interference suppression for MU-MIMO |
Intel Corporation |
R4-2204525 |
Discussion on R17 demodulation enhancement for intra-cell inter-user interference suppressing |
CMCC |
R4-2205499 |
Views on UE MMSE-IRC receiver for intra-cell inter-user interference suppression |
China Telecom |
R4-2205506 |
Remaining issues on MMSE-IRC receiver for intra-cell inter-user interference |
Ericsson |
R4-2205507 |
Simulation results on PDSCH performance for intra-cell inter-user interference |
Ericsson |
R4-2205794 |
Remain issues on MU-MIMO MMSE-IRC receiver |
Huawei,HiSilicon |
R4-2205795 |
Simulation results on MU-MIMO MMSE-IRC receiver |
Huawei,HiSilicon |
R4-2205796 |
Draft CR: Introduction of MU-MIMO Beamforming model in TS 38.101-4 |
Huawei,HiSilicon |
R4-2205797 |
Summary of simulation results for intra cell inter user MMSE-IRC receiver requirements |
Huawei,HiSilicon |
R4-2205903 |
Discussion on the MMSE-IRC receiver for intra-cell interference |
MediaTek inc. |
R4-2206089 |
Views on Intra-cell Inter-user Interference Scenarios |
Qualcomm Incorporated |
R4-2207163 |
Email discussion summary for [102-e][323] NR_perf_enh2_Demod_Part2 |
Moderator (Intel) |
R4-2207241 |
Draft TR 38.833 v1.2.0: Further enhancement on NR demodulation performance |
China Telecom |
R4-2207249 |
TP to TR 38.833: Link level simulation results for Inter-user interference suppression for MU-MIMO |
Intel Corporation |
R4-2207436 |
Email discussion summary for [102-e][323] NR_perf_enh2_Demod_Part2 |
Moderator (Intel) |
10.12.2.3.1 |
General |
|
R4-2203769 |
Discussion on CRS-IM requirements |
Apple |
R4-2204381 |
CRS-IM requirements for 30 kHz SCS scenarios with overlapping spectrum for LTE and NR |
Intel Corporation |
R4-2204526 |
Discussion on the CRS-IM for NR 30kHz SCS |
CMCC |
R4-2204917 |
Discussion CRS-IM Feasibility for 30kHz SCS Scenario |
ZTE Corporation |
R4-2205435 |
Discussion on the general for CRS-IM |
Ericsson |
R4-2205494 |
draft LS on UE capability and network assistant signalling for CRS interference mitigation in scenarios with overlapping spectrum for LTE and NR |
China Telecom |
R4-2205798 |
Discussions on 30kHz CRS-IM receiver |
Huawei,HiSilicon |
R4-2206071 |
Views on the requirements for CRS-IM receiver |
MediaTek inc. |
R4-2206095 |
Views on CRS Interference Mitigation for 30kHz SCS in NR |
Qualcomm Incorporated |
R4-2207238 |
LS on UE capability and network assistant signalling for CRS interference mitigation in scenarios with overlapping spectrum for LTE and NR |
China Telecom |
10.12.2.3.2 |
Network assistant signaling |
|
R4-2203770 |
Discussion on Network Assistance Signalling for CRS-IM |
Apple |
R4-2204382 |
Network assistance signaling for CRS-IM receiver for scenarios with overlapping spectrum for LTE and NR |
Intel Corporation |
R4-2204527 |
Discussion on the network assistant signaling necessity for CRS-IM |
CMCC |
R4-2204833 |
On Necessity of Network assistant signalling for CRS-IM |
Nokia, Nokia Shanghai Bell |
R4-2204918 |
Network assistant signaling |
ZTE Corporation |
R4-2205433 |
Discussion on the network assistant signaling for CRS-IM |
Ericsson |
R4-2205495 |
Discussion on the network assistance signalling and UE capability for CRS-IM |
China Telecom |
R4-2205799 |
Discussions on NWA and capability signaliing for 15kHz CRS-IM receiver |
Huawei,HiSilicon |
10.12.2.3.3 |
Test set-up |
|
R4-2203771 |
Discussion on Test setup for CRS-IM requirements |
Apple |
R4-2204383 |
Test setup for CRS-IM receiver for scenarios with overlapping spectrum for LTE and NR |
Intel Corporation |
R4-2204528 |
Discussion on the test setup for CRS-IM |
CMCC |
R4-2204919 |
Test setup for 15 kHz SCS scenario |
ZTE Corporation |
R4-2205434 |
Discussion on the test set-up for CRS-IM |
Ericsson |
R4-2205496 |
Discussion on the test setup for CRS-IM requirement definition |
China Telecom |
R4-2205800 |
Discussion on test setup for 15kHz CRS-IM receiver |
Huawei,HiSilicon |
R4-2206052 |
On test setup for CRS-IM |
Nokia, Nokia Shanghai Bell |
R4-2206107 |
Views on Test Setup for CRS Interference Mitigation in NR |
Qualcomm Incorporated |
10.12.3 |
BS demodulation requirements |
|
R4-2207251 |
Big CR for TS38.141-2 FR1 PUSCH 256QAM |
Ericsson |
R4-2207253 |
BigCR for TS38.104: Introduction of conformance testing requirements for FR1 PUSCH 256QAM |
Nokia |
10.12.3.1 |
PUSCH demodulation requirements for FR1 256QAM |
|
R4-2203550 |
draft CR on FR1 PUSCH 256QAM FRC for TS 38.141-1 |
Samsung |
R4-2203551 |
draft CR on FR1 PUSCH 256QAM FRC for TS 38.141-2 |
Samsung |
R4-2204026 |
Big CR for TS38.141-2 FR1 PUSCH 256QAM |
Ericsson |
R4-2204529 |
Draft CR for TS38.141-2 Requirements for PUSCH with transform precoding disabled for BS type 1-O |
CMCC |
R4-2205127 |
Draft big CR for TS38.141-2 FR1 PUSCH 256QAM |
Ericsson |
R4-2205810 |
draft CR for FR1 PUSCH 256QAM requirements in TS 38.141-1 |
Huawei,HiSilicon |
R4-2205811 |
BigCR for FR1 PUSCH 256QAM requirements in TS 38.104 |
Huawei,HiSilicon |
R4-2205812 |
Summary of simulation results for FR1 PUSCH 256QAM performance requirements |
Huawei,HiSilicon |
R4-2205816 |
Draft CR for TS 38.104: FR1 256QAM PUSCH requirements |
Intel Corporation |
R4-2205824 |
BigCR for FR1 PUSCH 256QAM requirements in TS 38.141-1 |
Huawei,HiSilicon |
R4-2207164 |
Email discussion summary for [102-e][324] NR_perf_enh2_Demod_Part3 |
Moderator (Huawei) |
R4-2207229 |
draft CR: FRC for PDSCH demodulation requirement for FR2 HST |
Ericsson |
R4-2207233 |
draft CR: FRC for CA PDSCH demodulation requirements for HST |
Ericsson |
R4-2207252 |
Draft CR for TS 38.104: FR1 256QAM PUSCH requirements |
Intel |
R4-2207437 |
Email discussion summary for [102-e][324] NR_perf_enh2_Demod_Part3 |
Moderator (Huawei) |
10.13.1 |
General |
|
R4-2203964 |
UE feature for NTN |
CATT |
R4-2205232 |
TP TR 38.863 7.4.1 NTN UE Requirement (General) |
HUGHES Network Systems Ltd |
R4-2205437 |
TP to TR 38.108 on 4.5 Regional Requirement |
HUGHES Network Systems Ltd |
R4-2205472 |
TP for TS 38.101-5: Genera(5.1) and Operating Band(5.2) |
ZTE Corporation |
R4-2205476 |
TP for TS 38.108: Genera(5.1) and Operating Band(5.2) |
ZTE Corporation |
R4-2207165 |
Email discussion summary for [102-e][308] NTN_Solutions_Part1 |
Moderator (THALES) |
R4-2207215 |
DraftCR to TS 38.174: Introduction of conducted transmitter requirements for eIAB |
Nokia, Nokia Shanghai Bell |
R4-2207219 |
DraftCR on for TS 38.104 for >52.6 GHz on clauses 10.1 – 10.5 |
CATT |
R4-2207228 |
DraftCR to TS 38.101-4: Applicability rules for HST FR2 PDSCH requirements |
Intel |
R4-2207247 |
draftCR to TS 38.101-4: NR Interference model for enhanced performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2207248 |
draftCR on CSI reporting test case(TDD) |
Ericsson |
R4-2207257 |
draftCR: Updates to NPDSCH repetition number for LTE NPDSCH requirements with multi-TB interleaved transmission (Rel-16) |
Huawei,HiSilicon |
R4-2207288 |
Draft TP to TS 38.106: Frequency stability and out of band gain requirements |
Ericsson |
R4-2207330 |
TP TR 38.863 7.4.1 NTN UE Requirement (General) |
HUGHES Network Systems Ltd |
R4-2207334 |
TP for TS 38.101-5: General (5.1) and Operating Band (5.2) |
ZTE Corporation |
R4-2207335 |
TP for TS 38.108: Genera(5.1) and Operating Band(5.2) |
ZTE Corporation |
R4-2207336 |
Draft text proposal for Clause 4.4 Satellite Access Node classes - TS 38.108 |
Ericsson |
R4-2207340 |
TP to TR 38.108 on 4.5 Regional Requirement |
HUGHES Network Systems Ltd |
R4-2207342 |
Draft text proposal for Annex B - TS 38.108 |
THALES |
R4-2207343 |
Draft text proposal for Clause 3 - TS 38.101-5 |
THALES |
R4-2207344 |
Draft text proposal for Clause 4 - TS 38.101-5 |
THALES |
R4-2207345 |
Draft text proposal for Clauses 7, 7.1, 7.2, 7.3 in TR 38.863 |
THALES |
R4-2207346 |
Way Forward on NTN_solutions_Part1 |
THALES |
R4-2207351 |
Draft text proposal to update TR 38.863 Chapter 6 |
Samsung |
R4-2207352 |
Draft text proposal for Clauses 6.4 and 6.5 in TR 38.863 to correct conclusions from simulation results based on AAS antenna assumption |
THALES |
R4-2207353 |
Draft text proposal for Clauses 6.4 and 6.5 in TR 38.863 to include simulation results based on Non-AAS antenna assumption |
THALES |
R4-2207360 |
Draft text proposal for Clause 7.3.4.7.3 OTA ACLR in TR 38.863 |
THALES |
R4-2207367 |
Draft text proposal for Clause 7.3.5.6 OTA Out-of-band blocking in TR 38.863 |
THALES |
R4-2207372 |
Draft text proposal for Clause 6.1 and 6.2 Satellite Access Node output power - TS 38.108 |
THALES |
R4-2207375 |
Draft TP for TS 38.108 Section 6.6.4 Operating band unwanted emissions |
Inmarsat |
R4-2207379 |
Draft text proposal for Clause 7.3.3.2.4 Out-of-band blocking in TR 38.863 |
THALES |
R4-2207380 |
Draft text proposal for Clause 7.5 Out-of-band blocking - TS 38.108 |
THALES |
R4-2207381 |
Draft text proposal for Clauses 7.3.3.2.3.1 Adjacent Channel Selectivity (ACS) and 7.3.3.2.3.2 In-band blocking in TR 38.863 |
THALES |
R4-2207386 |
Draft text proposal for Clause 7.3.2.2.4.1 ACLR in TR 38.863 |
THALES |
R4-2207395 |
Draft text proposal to update TS 38.101-5 Chapter 1 |
Samsung R&D Institute UK |
R4-2207398 |
Draft TP to update TR 38.863 clause 7.4.3.2 on NTN UE ACS |
Mediatek India Technology Pvt. |
R4-2207399 |
Draft TP to update TR 38.863 clause 7.4.3.2 on Blocking characteristics |
Mediatek India Technology Pvt. |
R4-2207438 |
Email discussion summary for [102-e][308] NTN_Solutions_Part1 |
Moderator (THALES) |
R4-2207457 |
DraftCR on for TS 38.104 for >52.6 GHz licensed operation |
Ericsson |
R4-2207460 |
Draft text proposal for Clause 7.3.2.2.4.1 ACLR in TR 38.86 |
THALES |
R4-2207513 |
Draft TS 38.108 v0.1.0 |
Thales |
R4-2207514 |
Draft TS 38.101-5 v0.1.0 |
Samsung |
R4-2207515 |
Draft TR 38.863 v0.3.0 |
Samsung |
10.13.1.1 |
System parameters |
|
R4-2203953 |
TP for 38.108: clause 5.3&5.4 on system parameters |
CATT |
R4-2204507 |
TP on TS 38.101-5 for UE channel bandwidth and channel arrangement |
Qualcomm Incorporated |
R4-2205554 |
On NTN System parameters |
Nokia, Nokia Shanghai Bell |
R4-2207331 |
TP for 38.108: clause 5.3&5.4 on system parameters |
CATT |
R4-2207332 |
TP on TS 38.101-5 for UE channel bandwidth and channel arrangement |
Qualcomm Incorporated |
10.13.1.2 |
NTN Satellite Access Node Class/Type |
|
R4-2205048 |
NTN - SAN class |
Ericsson |
R4-2205673 |
Draft text proposal for Clause 4.3 Requirement reference points - TS 38.108 |
THALES |
R4-2205730 |
Draft text proposal for Clause 4.4 Satellite Access Node classes - TS 38.108 |
THALES |
10.13.1.3 |
Regulatory information |
|
R4-2205111 |
TP for TR 38.863: Regulatory aspects for NTN satellite access nodes and UEs operating in UL1626.5-1660.5 MHz and DL 1525-1559 MHz frequencies ranges |
Ligado Networks |
R4-2205314 |
TP to TR 38.863 on Section 5.2 NTN Satellite band |
HUGHES Network Systems Ltd |
R4-2205555 |
TP to TR 38.863 Regulatory aspects for HAPS |
Nokia, Nokia Shanghai Bell |
R4-2205733 |
Draft text proposal for Clause 4.5 Regional requirements - TS 38.108 |
THALES |
R4-2207333 |
TP to TR 38.863 on Section 5.2 NTN Satellite band |
HUGHES Network Systems Ltd |
R4-2207338 |
TP for TR 38.863: Regulatory aspects for NTN satellite access nodes and UEs operating in UL1626.5-1660.5 MHz and DL 1525-1559 MHz frequencies ranges |
Ligado Networks |
R4-2207339 |
TP to TR 38.863 Regulatory aspects for HAPS |
Nokia, Nokia Shanghai Bell |
10.13.1.4 |
Others |
|
R4-2203536 |
Considerations on HAPS operating band(s) |
SoftBank, Deutsche Telekom, Ericsson, NTT Docomo, KDDI, Nokia, Intelsat |
R4-2203952 |
TP for 38.108: clause 4.3 requirement reference point |
CATT |
R4-2204195 |
CR for TS 38.104: capturing HAPS requirements |
Softbank, Deutsche Telekom, Ericsson, NTT Docomo, KDDI, Nokia, Intelsat |
R4-2205051 |
NTN - General aspect related to TS assumptions |
Ericsson |
R4-2205667 |
Draft text proposal for Annex B - TS 38.108 |
THALES |
R4-2205671 |
Draft text proposal for Clause 3 - TS 38.101-5 |
THALES |
R4-2205672 |
Draft text proposal for Clause 4 - TS 38.101-5 |
THALES |
R4-2205921 |
Draft text proposal for Clauses 7, 7.1, 7.2, 7.3 in TR 38.863 |
THALES |
R4-2207337 |
TP for 38.108: clause 4.3 requirement reference point |
CATT |
R4-2207341 |
CR for TS 38.104: capturing HAPS requirements |
Softbank, Deutsche Telekom, Ericsson, NTT Docomo, KDDI, Nokia, Intelsat |
10.13.2 |
Coexistence aspects |
|
R4-2204333 |
Draft text proposal to update TR 38.863 Chapter 6 |
Samsung |
R4-2207166 |
Email discussion summary for [102-e][309] NTN_Solutions_Part2 |
Moderator (Samsung) |
R4-2207347 |
WF on [309] NTN_Solutions_Part2 |
Samsung |
R4-2207439 |
Email discussion summary for [102-e][309] NTN_Solutions_Part2 |
Moderator (Samsung) |
10.13.2.1 |
NTN coexistence scenarios and simulations |
|
R4-2204502 |
Coexistence simulation results for TN-NTN case 1 |
Qualcomm Incorporated |
R4-2205044 |
NTN - Coexistence simulation results |
Ericsson |
R4-2205913 |
Draft text proposal for Clauses 6.4 and 6.5 in TR 38.863 to correct conclusions from simulation results based on AAS antenna assumption |
THALES |
R4-2205914 |
Draft text proposal for Clauses 6.4 and 6.5 in TR 38.863 to include simulation results based on Non-AAS antenna assumption |
THALES |
R4-2205924 |
On the ACIR selection and ACIR average computation between companies |
THALES |
10.13.2.2 |
HAPS coexistence scenarios and simulations |
|
R4-2204503 |
Coexistence simulation results for HAPS |
Qualcomm Incorporated |
R4-2205284 |
Discussion on HAPS requirements |
Huawei, HiSilicon |
R4-2205556 |
HAPS coexistence simulation results |
Nokia, Nokia Shanghai Bell |
R4-2205557 |
TP to TR 38.863 on HAPS simulation update |
Nokia, Nokia Shanghai Bell |
10.13.2.3 |
ACLR/ACS proposals |
|
R4-2205045 |
NTN - SAN ACS and case 6 |
Ericsson |
R4-2205104 |
Discussion on GEO SAN ACLR |
Ligado Networks, Inmarsat |
R4-2205558 |
HAPS BS ACLR and ACS requirements |
Nokia, Nokia Shanghai Bell |
R4-2205925 |
On the applicability of rural SAN ACS requirements for urban TN deployment in the case of GEO |
THALES |
10.13.3 |
Satellite Access Node RF requirements |
|
R4-2205054 |
pCR to TS 38.108 - Scope and general |
Ericsson |
R4-2205976 |
TP to TS 38.108: section 4 |
Huawei, HiSilicon |
R4-2206121 |
TP to TS 38.108: section 3 |
Huawei, HiSilicon |
R4-2207387 |
WF on open issue for SAN |
Thales |
R4-2207456 |
WF on SAN SEM and spurious emission |
Thales, ZTE |
10.13.3.1 |
TX requirements for radiated characteristics |
|
R4-2203948 |
Open issue for Tx RF requriements for SAN type 1-O |
CATT |
R4-2203956 |
TP for 38.108: clause 9.3 OTA Satellite Access Node output power |
CATT |
R4-2203957 |
TP for 38.108: clause 9.7 OTA unwanted emissions |
CATT |
R4-2205057 |
pCR to TS 38.108 -Radiated Tx general and transmit power |
Ericsson |
R4-2205477 |
TP for TS 38.108 OTA output power dynamics(9.4) |
ZTE Corporation |
R4-2205848 |
Draft text proposal for Clause 7.3.4.7.3 OTA ACLR in TR 38.863 |
THALES |
R4-2205878 |
Draft text proposal for Clause 9.3 OTA Satellite Access Node output power - TS 38.108 |
THALES |
R4-2205880 |
Draft text proposal for Clause 9.6 OTA transmitted signal quality - TS 38.108 |
THALES |
R4-2205886 |
Draft text proposal for Clause 9.7.3 OTA Adjacent Channel Leakage Power Ratio (ACLR) - TS 38.108 |
THALES |
R4-2205977 |
Further discussion on Satellite Access Node radiated RF requirements: Tx |
Huawei, HiSilicon |
R4-2205978 |
Discussion on the AAS architecture and consideration of the emissions scaling |
Huawei, HiSilicon |
R4-2205979 |
TP to TS 38.108: 9.5 (OTA Tx ON/OFF), 9.6 (OTA TX signal quality) and 9.8 (OTA Tx IMD) |
Huawei, HiSilicon |
R4-2207167 |
Email discussion summary for [102-e][310] NTN_Solutions_Part3 |
Moderator (CATT) |
R4-2207357 |
TP for 38.108: clause 9.7 OTA unwanted emissions |
CATT |
R4-2207359 |
TP for TS 38.108 OTA output power dynamics(9.4) |
ZTE Corporation |
R4-2207362 |
TP for 38.108: clause 9.3 OTA Satellite Access Node output power |
CATT |
R4-2207376 |
TP for 38.108: clause 7.1&7.2 on Rx refsens sensitivity |
CATT |
R4-2207440 |
Email discussion summary for [102-e][310] NTN_Solutions_Part3 |
Moderator (CATT) |
10.13.3.2 |
RX requirements for radiated characteristics |
|
R4-2203949 |
Open issue for Rx RF requriements for SAN type 1-O |
CATT |
R4-2203958 |
TP for 38.108: clause 10.5 OTA in-band selectivity and blocking |
CATT |
R4-2205049 |
NTN - SAN OTA RX requirement proposals |
Ericsson |
R4-2205058 |
pCR to TS 38.108 - Radiated Rx general and sensitivity |
Ericsson |
R4-2205285 |
Discussion on ACS for NR NTN SAN |
Huawei, HiSilicon |
R4-2205478 |
TP for TS 38.108 OTA Rx requirements(10.3, 10.4,10.6 and 10.9) |
ZTE Corporation |
R4-2205851 |
Draft text proposal for Clause 7.3.5.6 OTA Out-of-band blocking in TR 38.863 |
THALES |
R4-2205897 |
Draft text proposal for Clause 10.5 OTA in-band selectivity (ACS) and OTA in-band blocking - TS 38.108 |
THALES |
R4-2205899 |
Draft text proposal for Clause 10.6 OTA out-of-band blocking - TS 38.108 |
THALES |
R4-2205980 |
Further discussion on Satellite Access Node radiated RF requirements: Rx |
Huawei, HiSilicon |
R4-2205981 |
TP to TS 38.108: section 10.7 (OTA Rx spur) and 10.8 (OTA Rx IMD) |
Huawei, HiSilicon |
R4-2207364 |
TP for 38.108: clause 10.5 OTA in-band selectivity and blocking |
CATT |
R4-2207366 |
TP for TS 38.108 OTA Rx requirements(10.3, 10.4,10.6 and 10.9) |
ZTE Corporation |
10.13.3.3 |
Tx requirements for conducted characteristics |
|
R4-2203950 |
Open issue for Tx RF requriements for SAN type 1-H |
CATT |
R4-2203954 |
TP for 38.108: clause 6.6.1&6.6.2&6.6.3 unwanted emissions |
CATT |
R4-2205046 |
NTN - SAN TX requirement proposals |
Ericsson |
R4-2205055 |
pCR to TS 38.108 - Transmitter spurious emissions |
Ericsson |
R4-2205445 |
TP to TS 38.108 on 6.0 Conducted transmitter characteristics |
HUGHES Network Systems Ltd |
R4-2205468 |
Discussion on conducted Tx requirements of satellite access node |
ZTE Corporation |
R4-2205479 |
TP for TS 38.108: Output power dynamics (6.3) |
ZTE Corporation |
R4-2205813 |
Draft text proposal for Clause 6.1 and 6.2 Satellite Access Node output power - TS 38.108 |
THALES |
R4-2205823 |
Draft text proposal for Clause 6.5.2 Modulation quality - TS 38.108 |
THALES |
R4-2205825 |
Draft text proposal for Clause 6.6.3 Adjacent Channel Leakage Power Ratio - TS 38.108 |
THALES |
R4-2205827 |
Draft text proposal for Clause 7.3.2.2.4.1 ACLR in TR 38.863 |
THALES |
R4-2205982 |
Further discussion on Satellite Access Node conducted RF requirements: Tx |
Huawei, HiSilicon |
R4-2205983 |
TP to TS 38.108: section 6.4 (Tx ON/OFF) and 6.5 (TX signal quality) |
Huawei, HiSilicon |
R4-2205984 |
TP to TS 38.108: section 6.7 (Tx IMD) |
Huawei, HiSilicon |
R4-2206117 |
Draft TP for TS 38.108 Section 6.6.4 Operating band unwanted emissions |
Inmarsat |
R4-2207356 |
TP to TS 38.108: section 3 |
Huawei, HiSilicon |
R4-2207361 |
TP to TS 38.108: 9.5 (OTA Tx ON/OFF), 9.6 (OTA TX signal quality) and 9.8 (OTA Tx IMD) |
Huawei, HiSilicon |
R4-2207368 |
TP to TS 38.108: section 10.7 (OTA Rx spur) and 10.8 (OTA Rx IMD) |
Huawei, HiSilicon |
R4-2207369 |
TP for 38.108: clause 6.6.1&6.6.2&6.6.3 unwanted emissions |
CATT |
R4-2207370 |
TP to TS 38.108 on 6.0 Conducted transmitter characteristics |
HUGHES Network Systems Ltd |
R4-2207371 |
TP for TS 38.108: Output power dynamics (6.3) |
ZTE Corporation |
R4-2207383 |
TP to TS 38.108: annex A (FRC) |
Huawei, HiSilicon |
10.13.3.4 |
Rx requirements for conducted characteristics |
|
R4-2203951 |
Open issue for Rx RF requriements for SAN type 1-H |
CATT |
R4-2203955 |
TP for 38.108: clause 7.1&7.2 on Rx refsens sensitivity |
CATT |
R4-2205047 |
NTN - SAN RX requirement proposals |
Ericsson |
R4-2205056 |
pCR to TS 38.108 - In-band selectivity and blocking |
Ericsson |
R4-2205469 |
Discussion on conducted RF requirements from satellite network perspective |
ZTE Corporation |
R4-2205474 |
TP for TS 38.108 Annex B |
ZTE Corporation |
R4-2205475 |
TP for TS 38.108 Dynamic range(7.3) and In channel selectivity(7.8) |
ZTE Corporation |
R4-2205847 |
Draft text proposal for Clause 7.3.3.2.4 Out-of-band blocking in TR 38.863 |
THALES |
R4-2205864 |
Draft text proposal for Clause 7.4.1 Adjacent Channel Selectivity (ACS) and Clause 7.4.2 In-band blocking - TS 38.108 |
THALES |
R4-2205866 |
Draft text proposal for Clause 7.5 Out-of-band blocking - TS 38.108 |
THALES |
R4-2205922 |
Draft text proposal for Clauses 7.3.3.2.3.1 Adjacent Channel Selectivity (ACS) and 7.3.3.2.3.2 In-band blocking in TR 38.863 |
THALES |
R4-2205985 |
Further discussion on Satellite Access Node conducted RF requirements: Rx |
Huawei, HiSilicon |
R4-2205986 |
TP to TS 38.108: section 7.6 (Rx spur) and section 7.7 (Rx IMD) |
Huawei, HiSilicon |
R4-2205987 |
TP to TS 38.108: annex A (FRC) |
Huawei, HiSilicon |
R4-2207355 |
TP to TS 38.108: section 4 |
Huawei, HiSilicon |
R4-2207363 |
TP for TS 38.108 Annex B |
ZTE Corporation |
R4-2207373 |
TP to TS 38.108: section 6.4 (Tx ON/OFF) and 6.5 (TX signal quality) |
Huawei, HiSilicon |
R4-2207374 |
TP to TS 38.108: section 6.7 (Tx IMD) |
Huawei, HiSilicon |
R4-2207378 |
TP for TS 38.108 Dynamic range(7.3) and In channel selectivity(7.8) |
ZTE Corporation |
R4-2207382 |
TP to TS 38.108: section 7.6 (Rx spur) and section 7.7 (Rx IMD) |
Huawei, HiSilicon |
10.13.4 |
UE RF requirements |
|
R4-2204344 |
Draft text proposal to update TS 38.101-5 Chapter 1 |
Samsung R&D Institute UK |
R4-2204592 |
Draft TP to update TR 38.863 clause 7.4.3.2 on NTN UE ACS |
Mediatek India Technology Pvt. |
R4-2204593 |
Draft TP to update TR 38.863 clause 7.4.3.2 on Blocking characteristics |
Mediatek India Technology Pvt. |
R4-2205052 |
pCR to TS 38.101-5 - Scope |
Ericsson |
R4-2205608 |
TP to TS 38.101-5 on 7.3 Reference sensitivity |
HUGHES Network Systems Ltd |
R4-2205654 |
Selection of UE duplexer and REFSENS for band n256 in TS 38.101-5 |
HUGHES Network Systems Ltd |
R4-2207412 |
TP to TS 38.101-5 on 7.3 Reference sensitivity |
HUGHES Network Systems Ltd |
R4-2207416 |
WF on NTN UE RF requirement |
ZTE Corporation |
10.13.4.1 |
TX requirements |
|
R4-2203863 |
Discussion on NTN TX spurious emission for UE co-existence |
Mediatek India Technology Pvt. |
R4-2203926 |
Further discussion on UE Tx RF requirements for NTN |
CATT |
R4-2203959 |
TP for 38.101-5: clause 6.3 output power dynamics |
CATT |
R4-2203960 |
TP for 38.863: clause 7.3.2 Conducted transmission characteristics |
CATT |
R4-2204329 |
TP for 38.101-5: clause 6.4 transmit signal qulity |
CATT |
R4-2204504 |
Discussion on NTN UE RF requirements |
Qualcomm Incorporated |
R4-2204505 |
TP on TS 38.101-5 for general part of transmitter characteristics |
Qualcomm Incorporated |
R4-2204506 |
TP on TR 38.863 for NTN UE Tx requirements |
Qualcomm Incorporated |
R4-2204807 |
TP for TS38.101-5 on section 6.2 transmitter power |
Xiaomi |
R4-2204808 |
TP for 38.863 on MPR and A-MPR requirement for NTN UE |
Xiaomi |
R4-2204809 |
Discussion on MPR and A-MPR requirements for NTN UE |
Xiaomi |
R4-2205043 |
TP for TR 38.863: Unwanted emissions for NTN satellite UEs transmitting in 1626.5 to 1660.5 MHz |
Ligado Networks |
R4-2205050 |
NTN - UE RF Tx requirements |
Ericsson |
R4-2205110 |
TP for TR 38.863: Updates to UE Maximum Output Power for n255 |
Ligado Networks, Inmarsat |
R4-2205235 |
pCR for TS 38.101-5: NS value and additional spurious requirements for n255 |
Ligado Networks |
R4-2205286 |
Discussion on UE Tx requirements for satellite access |
Huawei, HiSilicon |
R4-2205288 |
TP for 38.863 on UE transmitter characteristics for satellite access |
Huawei, HiSilicon |
R4-2205290 |
TP for 38.101-5 on Output RF spectrum emissions for satellite UE |
Huawei, HiSilicon |
R4-2205470 |
Discussion on NTN UE Tx RF requirements |
ZTE Corporation |
R4-2207168 |
Email discussion summary for [102-e][311] NTN_Solutions_Part4 |
Moderator (ZTE) |
R4-2207231 |
Simulation assumption for PDSCH requirement |
intel |
R4-2207319 |
Test lab and device information for lab alignment activity |
vivo |
R4-2207348 |
Simulation assumptions for NTN co-existence |
Samsung, CATT |
R4-2207349 |
Summary of NTN co-existence study |
Samsung |
R4-2207350 |
Summary of HAPS co-existence study |
Nokia |
R4-2207354 |
pCR to TS 38.108 - Scope and general |
Ericsson |
R4-2207358 |
pCR to TS 38.108 -Radiated Tx general and transmit power |
Ericsson |
R4-2207365 |
pCR to TS 38.108 - Radiated Rx general and sensitivity |
Ericsson |
R4-2207377 |
pCR to TS 38.108 - In-band selectivity and blocking |
Ericsson |
R4-2207384 |
pCR to TS 38.108 - Transmitter spurious emissions |
Ericsson |
R4-2207388 |
Operating band unwanted emissions |
THALES |
R4-2207389 |
SAN spurious emissions |
Thales |
R4-2207390 |
SAN ICS requirements |
Thales |
R4-2207391 |
TP for 38.101-5: clause 6.3 output power dynamics |
CATT |
R4-2207396 |
TP on TS 38.101-5 for general part of transmitter characteristics |
Qualcomm Incorporated |
R4-2207397 |
TP on TR 38.863 for NTN UE Tx requirements |
Qualcomm Incorporated |
R4-2207403 |
TP for TR 38.863: Unwanted emissions for NTN satellite UEs transmitting in 1626.5 to 1660.5 MHz |
Ligado Networks |
R4-2207404 |
pCR to TS 38.101-5 - Scope |
Ericsson |
R4-2207405 |
pCR to TS 38.101-5 - Receiver requirements general |
Ericsson |
R4-2207406 |
TP for TR 38.863: Updates to UE Maximum Output Power for n255 |
Ligado Networks, Inmarsat |
R4-2207407 |
pCR for TS 38.101-5: NS value and additional spurious requirements for n255 |
Ligado Networks |
R4-2207409 |
TP for 38.101-5 on Output RF spectrum emissions for satellite UE |
Huawei, HiSilicon |
R4-2207413 |
TP for 38.101-5: clause 6.4 transmit signal qulity |
CATT |
R4-2207415 |
TP for TS38.101-5 on section 6.2 transmitter power |
Xiaomi |
R4-2207441 |
Email discussion summary for [102-e][311] NTN_Solutions_Part4 |
Moderator (ZTE) |
R4-2207462 |
TP for 38.101-5 on Output RF spectrum emissions for satellite UE |
Huawei, HiSilicon |
10.13.4.2 |
RX requirements |
|
R4-2203864 |
Discussion on UE RX REFSENS for NTN |
Mediatek India Technology Pvt. |
R4-2203927 |
Further discussion on UE Rx RF requirements for NTN |
CATT |
R4-2204169 |
TP to TS 38.101-5 on clause 7.5 NTN UE ACS |
Mediatek India Technology Pvt. |
R4-2204170 |
TP to TS 38.101-5 on clause 7.6 Blocking characteristics |
Mediatek India Technology Pvt. |
R4-2204810 |
TP for TS38.101-5 on section 7.8 Intermodulation characteristics |
Xiaomi |
R4-2204811 |
TP for 38.863 on Intermodulation characteristics for NTN UE |
Xiaomi |
R4-2204812 |
TP for 38.863 on spurious response for NTN UE |
Xiaomi |
R4-2205053 |
pCR to TS 38.101-5 - Receiver requirements general |
Ericsson |
R4-2205287 |
Discussion on UE Rx requirements for satellite access |
Huawei, HiSilicon |
R4-2205289 |
TP for 38.863 on UE Receiver characteristics for satellite access |
Huawei, HiSilicon |
R4-2205291 |
TP for 38.101-5 on Rx Spurious emissions and spurious response for satellite UE |
Huawei, HiSilicon |
R4-2205471 |
Discussion on NTN UE Rx RF requirements |
ZTE Corporation |
R4-2205473 |
TP for TS 38.101-5: Maximum input level (7.4) |
ZTE Corporation |
R4-2207392 |
TP for 38.863: clause 7.3.2 Conducted transmission characteristics |
CATT |
R4-2207393 |
TP to TS 38.101-5 on clause 7.5 NTN UE ACS |
Mediatek India Technology Pvt. |
R4-2207400 |
TP for TS38.101-5 on section 7.8 Intermodulation characteristics |
Xiaomi |
R4-2207401 |
TP for 38.863 on Intermodulation characteristics for NTN UE |
Xiaomi |
R4-2207402 |
TP for 38.863 on spurious response for NTN UE |
Xiaomi |
R4-2207410 |
TP for 38.101-5 on Rx Spurious emissions and spurious response for satellite UE |
Huawei, HiSilicon |
R4-2207411 |
TP for TS 38.101-5: Maximum input level (7.4) |
ZTE Corporation |
R4-2207414 |
TP for 38.863 on UE Receiver characteristics for satellite access |
Huawei, HiSilicon |
10.13.5.1 |
General |
|
R4-2203853 |
General and RRM requirements impacts |
Qualcomm Incorporated |
R4-2203854 |
draft Cat-B CR (R17) MDT in NTN |
Qualcomm Incorporated |
R4-2203928 |
Further discussion on general RRM requirements for NTN |
CATT |
R4-2203929 |
Requirements for RRC connected state mobility for NTN |
CATT |
R4-2204185 |
Discussion on general RRM requirements in NTN |
MediaTek inc. |
R4-2204295 |
Discussion on general RRM requirements for NTN |
OPPO |
R4-2204520 |
Discussion on NTN general requirements |
LG Electronics UK |
R4-2204722 |
General requirements for NTN |
Ericsson |
R4-2204725 |
draft CR on signaling characteristics for NTN |
Ericsson |
R4-2205374 |
Discussion on general issues for NTN RRM |
Huawei, HiSilicon |
R4-2205422 |
Reply LS to RAN1: LS on open loop closed loop dual correction of timing |
Ericsson |
R4-2206763 |
Email discussion summary for [102-e][220] NR_NTN_solutions_RRM_1 |
Moderator (Qualcomm) |
R4-2206899 |
WF on NR NTN RRM requirements |
Qualcomm |
R4-2206900 |
draft CR on signaling characteristics for NTN |
Ericsson |
R4-2207061 |
Email discussion summary for [102-e][220] NR_NTN_solutions_RRM_1 |
Moderator (Qualcomm) |
R4-2207114 |
WF on NR NTN RRM requirements |
Qualcomm |
R4-2207120 |
Big CR: RRM requirements for Rel-17 NR NTN |
Qualcomm |
10.13.5.2 |
GNSS-related requirements |
|
R4-2206903 |
WF on GNSS-related and timing requirements for NR NTN |
Xiaomi |
R4-2206904 |
Reply LS on NTN UL time and frequency synchronization requirements |
Xiaomi |
R4-2206905 |
Reply LS on combination of open and closed loop TA control in NTN |
Qualcomm |
10.13.5.3 |
Mobility requirements |
|
R4-2203793 |
Discussion on CHO for NR NTN |
Apple |
R4-2203855 |
Mobility requirements |
Qualcomm Incorporated |
R4-2203930 |
Further discussion on mobility requirements for NTN |
CATT |
R4-2204236 |
Further discussion on mobility requirements for NR NTN |
Xiaomi |
R4-2204237 |
DraftCR on maximum interruption in paging reception for NR NTN |
Xiaomi |
R4-2204296 |
Discussion on mobility requirements for NTN |
OPPO |
R4-2204418 |
Discussion on CHO delay requirements for NTN UE |
Intel Corporation |
R4-2204421 |
DraftCR for serving cell evaluation and intra-frequency measurements of NTN UE cell reselections |
Intel Corporation |
R4-2204474 |
Draft CR for idle mode UE meausrement capability in NTN. |
LG Electronics UK |
R4-2204522 |
Discussion on NTN Mobility requirements |
LG Electronics UK |
R4-2204724 |
Mobility requirements for NTN |
Ericsson |
R4-2205228 |
NTN CHO timeline considerations |
Nokia, Nokia Shanghai Bell |
R4-2205375 |
Discussion on mobility requirements for NTN RRM |
Huawei, HiSilicon |
R4-2205376 |
CR on IDLE mode mobility requirements for NTN |
Huawei, HiSilicon |
R4-2206901 |
DraftCR for serving cell evaluation and intra-frequency measurements of NTN UE cell reselections |
Intel Corporation |
R4-2206902 |
CR on IDLE mode mobility requirements for NTN |
Huawei, HiSilicon |
10.13.5.4 |
Timing requirements |
|
R4-2203794 |
Discussion on timing requirements for NR NTN |
Apple |
R4-2203856 |
Timing requirements |
Qualcomm Incorporated |
R4-2203931 |
Further discussion on timing requirements for NTN |
CATT |
R4-2204160 |
Discussion on timing requirements for NTN UE |
ZTE Corporation |
R4-2204186 |
Discussion on timing requirements in NTN |
MediaTek inc. |
R4-2204187 |
Introduction of Timing advance requirement for NTN |
MediaTek inc. |
R4-2204238 |
Further discussion on timing requirements for NR NTN |
Xiaomi |
R4-2204239 |
DraftCR on UE timer accuracy for NR NTN |
Xiaomi |
R4-2204316 |
Discussion on NTN timing requirements |
LG Electronics Inc. |
R4-2204419 |
Discussion on the remaining issues for NTN timing requirements |
Intel Corporation |
R4-2204530 |
Discussion on NTN timing requirements |
CMCC |
R4-2205329 |
Discussion on NTN UE timing related requirements |
Huawei, HiSilicon |
R4-2205330 |
DraftCR on UE transmit timing requirements for NTN |
Huawei, HiSilicon |
R4-2205420 |
UE Timing requirements |
Ericsson |
R4-2205421 |
Reply LS to RAN1: LS on NTN UL time and frequency synchronization requirements (Timing) |
Ericsson |
R4-2206764 |
Email discussion summary for [102-e][221] NR_NTN_solutions_RRM_2 |
Moderator (Xiaomi) |
R4-2206906 |
Introduction of Timing advance requirement for NTN |
MediaTek inc. |
R4-2206907 |
DraftCR on UE timer accuracy for NR NTN |
Xiaomi |
R4-2206908 |
DraftCR on UE transmit timing requirements for NTN |
Huawei, HiSilicon |
R4-2207013 |
DraftCR to 38133 for interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2207014 |
DraftCR to 36133 for interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2207062 |
Email discussion summary for [102-e][221] NR_NTN_solutions_RRM_2 |
Moderator (Xiaomi) |
10.13.5.5 |
Measurement procedure requirements |
|
R4-2203795 |
Discussion on measurement procedure requirements for NTN |
Apple |
R4-2203857 |
Measurement procedure requirements |
Qualcomm Incorporated |
R4-2203932 |
Further discussion on measurement procedure requirements for NTN |
CATT |
R4-2204240 |
Further discussion on measurement requirements for NR NTN |
Xiaomi |
R4-2204241 |
DraftCR on inter-frequency measurement requirements for NR NTN |
Xiaomi |
R4-2204297 |
Draft CR to general measurement requirement for NTN |
OPPO |
R4-2204420 |
Discussion on multiple SMTC and measurement gaps for NTN UE |
Intel Corporation |
R4-2204545 |
Discussion on NTN measurement requirements |
LG Electronics UK |
R4-2204723 |
Measurement requirements for NTN |
Ericsson |
R4-2205230 |
Discussions on SMTC and measurement gaps |
Nokia, Nokia Shanghai Bell |
R4-2205377 |
Discussion on measurement requirements for NTN |
Huawei, HiSilicon |
R4-2205378 |
CR on intra-frequency measurement requirements for NTN |
Huawei, HiSilicon |
R4-2205958 |
Draft CR on L1-RSRP measurements for Reporting in NTN |
Apple |
10.13.6.1 |
General |
|
R4-2204027 |
Discussion on general issue of NTN demodulation |
Ericsson |
R4-2205763 |
Discussion on NTN general issues |
Huawei,HiSilicon |
R4-2207169 |
Email discussion summary for [102-e][325] NR_NTN_Demod |
Moderator (Qualcomm) |
R4-2207197 |
WF on general and NTN UE demodulation requirements |
Qualcomm |
R4-2207198 |
WF on NTN SAN demodulation requirements |
Huawei |
R4-2207442 |
Email discussion summary for [102-e][325] NR_NTN_Demod |
Moderator (Qualcomm) |
R4-2207463 |
WF on general and NTN UE demodulation requirements |
Qualcomm |
R4-2207464 |
WF on general and NTN UE demodulation requirements |
Qualcomm |
10.13.6.2 |
Satellite Access Node demodulation requirements |
|
R4-2206003 |
Discussion on Satellite Access Node demodulation requirements for NR NTN |
Intel Corporation |
10.13.6.2.1 |
PUSCH requirements |
|
R4-2204028 |
Discussion on NTN PUSCH demodulation |
Ericsson |
R4-2205764 |
Discussion on satellite NTN demod PUSCH |
Huawei,HiSilicon |
10.13.6.2.2 |
PUCCH requirements |
|
R4-2204029 |
Discussion on NTN PUCCH demodulation |
Ericsson |
R4-2205765 |
Discussion on satellite NTN demod PUCCH |
Huawei,HiSilicon |
10.13.6.2.3 |
PRACH requirements |
|
R4-2204030 |
Discussion on NTN PRACH demodulation |
Ericsson |
R4-2205766 |
Discussion on satellite NTN demod PRACH |
Huawei,HiSilicon |
10.13.6.3 |
UE demodulation requirements |
|
R4-2206004 |
Discussion on UE demodulation requirements for NR NTN |
Intel Corporation |
10.13.6.3.1 |
PDSCH requirements |
|
R4-2205430 |
Discussion on PDSCH requirements for NTN |
Ericsson |
R4-2205767 |
Discussion on UE NTN demod PDSCH |
Huawei,HiSilicon |
R4-2206123 |
Views on NTN UE PDSCH Requirements |
Qualcomm CDMA Technologies |
10.13.6.3.2 |
PDCCH/PBCH requirements |
|
R4-2205432 |
Discussion on PDCCH and PBCH requirements for NTN |
Ericsson |
R4-2205768 |
Discussion on UE NTN demod PDCCH&PBCH |
Huawei,HiSilicon |
10.13.6.4 |
CSI requirements |
|
R4-2205431 |
Discussion on CSI reporting requirements for NTN |
Ericsson |
R4-2205769 |
Discussion on UE NTN CSI |
Huawei,HiSilicon |
R4-2206126 |
Views on NTN UE CSI Tests |
Qualcomm CDMA Technologies |
10.14 |
UE Power Saving Enhancements for NR |
|
R4-2207087 |
ReplyLS to RAN2 on RLM/BFD relaxation for ePowSav |
Vivo |
10.14.1 |
General |
|
R4-2204531 |
Discussion on the UE feature for R17 RLM/BFD relaxation |
CMCC |
R4-2205636 |
Draft CR to TS 38.133: Applicability of relaxed BFD requirements |
Ericsson, MediaTek Inc. |
R4-2206765 |
Email discussion summary for [102-e][222] NR_UE_pow_sav_enh |
Moderator (MediaTek) |
R4-2206787 |
LS on RLM/BFD relaxation for NR UE power saving enhancements |
MediaTek inc. |
R4-2206790 |
LS on RLM/BFD relaxation for NR UE power saving enhancements |
MediaTek inc. |
R4-2206909 |
WF on RLM/BFD relaxation for UE Power Saving enhancements |
MediaTek Inc |
R4-2206914 |
Draft CR to TS 38.133: Applicability of relaxed BFD requirements |
Ericsson, MediaTek Inc. |
R4-2207012 |
Draft CR to TS 36.133 on SCG Activation and deactivation delay |
OPPO |
R4-2207063 |
Email discussion summary for [102-e][222] NR_UE_pow_sav_enh |
Moderator (MediaTek) |
R4-2207121 |
Big CR: RRM requirements Rel-17 NR UE Power Saving Enhancements |
MediaTek |
10.14.2 |
RRM core requirements |
|
R4-2203721 |
On Power Saving RRM Requirement |
Qualcomm, Inc. |
R4-2203757 |
UE measurements relaxation for RLM and/or BFD |
Apple |
R4-2203903 |
Further discussion on RLM/BFD relaxation for UE power saving enhancement |
CATT |
R4-2203904 |
Draft CR on relaxed measurement criteria for BFD |
CATT |
R4-2204243 |
Further discussion on UE measurements relaxation for RLM and/or BFD |
Xiaomi |
R4-2204280 |
Discussion on RRM requirements for R17 RLM/BFD relaxation |
OPPO |
R4-2204337 |
Discussion on remaining issues on RLM and BFD relaxation for NR UE power saving |
vivo |
R4-2204338 |
draft CR on CSI-RS RLM requirements relaxation for R17 UE power saving |
vivo |
R4-2204398 |
Discussion on UE power saving for RLM and BM |
Intel Corporation |
R4-2204532 |
Discussion on RLM/BFD relaxation for NR power saving enhancement |
CMCC |
R4-2204533 |
Draft CR for TS 38.133 Minimum requirement for SSB based BFD for UE configured with relaxed measurement criterion |
CMCC |
R4-2204706 |
Discussion about RLM/BFD measurement relaxation |
Nokia, Nokia Shanghai Bell |
R4-2204707 |
38.133 draft CR on RLM relaxation criteria |
Nokia, Nokia Shanghai Bell |
R4-2205331 |
Further discussion on RLM/BFD measurement relaxation |
Huawei, HiSilicon |
R4-2205332 |
DraftCR on SSB based relaxed RLM requirements |
Huawei, HiSilicon |
R4-2205402 |
RLM and RLF relaxation for UE power saving |
ZTE Corporation |
R4-2205637 |
Discussions on UE power saving for RLM and BFD |
Ericsson |
R4-2205642 |
Reply LS on Rel-16 UE power saving requirements |
Ericsson |
R4-2205643 |
Correction to Rel-16 UE relaxed measurement requirements |
Ericsson |
R4-2205659 |
Correction to Rel-16 UE relaxed measurement requirements |
Ericsson |
R4-2205660 |
Discussion on Rel-17 RLM/BFD measurement relaxation |
MediaTek inc. |
R4-2205661 |
CR on TS38.133 for applicability of RLM measurement relaxation |
MediaTek inc. |
R4-2205850 |
Clause title change on big CR |
Qualcomm communications-France |
R4-2206911 |
CR on TS38.133 for applicability of RLM measurement relaxation |
MediaTek inc. |
R4-2206912 |
DraftCR on SSB based relaxed RLM requirements |
Huawei, HiSilicon |
R4-2206913 |
draft CR on CSI-RS RLM requirements relaxation for R17 UE power saving |
vivo |
R4-2206915 |
Draft CR for TS 38.133 Minimum requirement for SSB based BFD for UE configured with relaxed measurement criterion |
CMCC |
R4-2206920 |
Draft CR on deriveSSB-IndexFromCell tolerance |
Qualcomm |
10.14.3 |
RRM performance requirements |
|
R4-2203722 |
On Power Saving RRM Performance Requirement Scope |
Qualcomm, Inc. |
R4-2203758 |
UE power saving enhancement: RRM performance requirements |
Apple |
R4-2203905 |
Discussion on RRM test cases for UE power saving enhancement |
CATT |
R4-2204534 |
Discussion on test cases for RLM/BFD measurement relaxation |
CMCC |
10.14.4 |
Demodulation performance requirements |
|
R4-2203759 |
UE power saving enhancement: demod performance requirements |
Apple |
R4-2204535 |
Discussion on demodulation for UE power saving enhancement |
CMCC |
R4-2205099 |
UE demodulation requirements for UE power saving enhancement |
Ericsson |
R4-2205770 |
Discussion on for power saving enhancement demod |
Huawei,HiSilicon |
R4-2205912 |
Views on demodulation requirements for power saving enhancements |
MediaTek inc. |
R4-2207170 |
Email discussion summary for [102-e][326] NR_UE_pow_sav_enh_Demod_NWM |
Moderator (MediaTek) |
R4-2207225 |
Way Forward on demodulation requirements for power saving enhancement |
MediaTek |
R4-2207443 |
Email discussion summary for [102-e][326] NR_UE_pow_sav_enh_Demod_NWM |
Moderator (MediaTek) |
10.15.1 |
General |
|
R4-2204152 |
TR38.785 v1.0.0 TR Update for SL enhancement in Rel-17 |
LG Electronics France |
R4-2204157 |
Formal big CR to introduce SL enhancements UE RF requirements in Rel-17 |
LG Electronics France |
R4-2206330 |
Email discussion summary for [102-e][130] NRSL_enh_Part_1 |
Moderator (LGE) |
R4-2206430 |
Email discussion summary for [102-e][130] NRSL_enh_Part_1 |
Moderator (LGE) |
10.15.2 |
UE RF requirements for NR SL enhancement |
|
R4-2204154 |
Draft CR on FRC for 5MHz CBW for SL enhancement for public safety service in n14 |
LG Electronics France |
R4-2204156 |
Draft big CR to merge the endorsed CRs for SL enhancement PS UE in Part1 |
LG Electronics France |
R4-2206294 |
Draft CR to 38.101-2: missing image location for CA IBE (cat. F) |
Qualcomm Incorporated |
R4-2206522 |
Draft CR on FRC for 5MHz CBW for SL enhancement for public safety service in n14 |
LG Electronics France |
R4-2206523 |
Draft big CR to merge the endorsed CRs for SL enhancement PS UE in Part1 |
LG Electronics France |
10.15.2.1 |
Configured Tx power requirements |
|
R4-2204929 |
Draft CR for TS 38.101-1, Correction on configured transmitted power for SL (Rel-16) |
vivo |
R4-2204930 |
Draft CR for TS 38.101-1, Correction on configured transmitted power for SL (Rel-17) |
vivo |
R4-2206590 |
Draft CR for TS 38.101-1, Correction on configured transmitted power for SL (Rel-16) |
Vivo |
10.15.2.3 |
Other RF requirements |
|
R4-2204017 |
Frequency error measurement period for NR SL MIMO and NR V2X TxD |
Qualcomm Incorporated |
R4-2205583 |
draft CR for TS 38.101-1: introduction of PC2 TxD for SL |
Huawei, HiSilicon |
R4-2206524 |
draft CR for TS 38.101-1: introduction of PC2 TxD for SL |
Huawei, HiSilicon |
10.15.3 |
Intra-band con-current operation between NR SUL and NR Uu |
|
R4-2204153 |
TP on the RF requirements for the remaining open issues for SL enhancements |
LG Electronics France |
R4-2205133 |
on Switching time mask |
Xiaomi |
R4-2206331 |
Email discussion summary for [102-e][131] NRSL_enh_Part_2 |
Moderator (CATT) |
R4-2206431 |
Email discussion summary for [102-e][131] NRSL_enh_Part_2 |
Moderator (CATT) |
R4-2206525 |
WF on switching time mask for intra-band V2X con-current operation |
CATT |
R4-2206526 |
LS on time mask for TDM NR Uu-SL intra-band concurrent switching |
Qualcomm |
R4-2206527 |
WF on MPR for intra-band V2X con-current operation |
Huawei, HiSilicon |
R4-2206528 |
TP on the RF requirements for the remaining open issues for SL enhancements |
LG Electronics France |
10.15.3.1 |
RF requirements for intra-band V2X con-current (including MPR) |
|
R4-2203912 |
Draft CR for TS 38.101-1, Remaining RF requirements for intra-band con-current operation |
CATT |
R4-2204144 |
MPR for NR V2X intra-band con-current operation with Uu |
LG Electronics |
R4-2204155 |
Draft CR on MPR and ON/OFF time mask for intra-band con-current V2X operation in Rel-17 |
LG Electronics France |
R4-2204174 |
Draft big CR for TS 38.101-1, RF requirements for intra-band con-current operation |
CATT, LGE |
R4-2204931 |
Further discussion on switching time mask for intra-band V2X con-current operation |
vivo |
R4-2205137 |
draft CR for TS 38.101-1 on switching time mask between SL and Uu |
Xiaomi |
R4-2205584 |
On MPR for intra-band con-current operation |
Huawei, HiSilicon |
R4-2206529 |
Draft CR for TS 38.101-1, Remaining RF requirements for intra-band con-current operation |
CATT |
R4-2206530 |
Draft CR on MPR and ON/OFF time mask for intra-band con-current V2X operation in Rel-17 |
LG Electronics France |
10.15.3.2 |
Synchronous operation between SL and Uu (including switching time mask, SL transmission timing) |
|
R4-2203911 |
Time mask for Uu and SL switching |
CATT |
R4-2204015 |
RF switching for V2X intra-band con-current operation with different carriers in TDD bands |
Qualcomm Incorporated |
R4-2204920 |
Synchronous operation between SL and Uu |
ZTE Corporation |
R4-2205135 |
TP to TR 38.785 switching time mask between SL and Uu for different carriers |
Xiaomi |
R4-2205136 |
draft CR for TS 38.101-1 on default power class for intra-band concurrent operation |
Xiaomi |
R4-2205585 |
On time mask for SL intra-band con-current operation |
Huawei, HiSilicon |
R4-2205586 |
draft CR for TS 38.101-1: On time mask for SL intra-band con-current operation |
Huawei, HiSilicon |
R4-2206531 |
TP to TR 38.785 switching time mask between SL and Uu for different carriers |
Xiaomi |
10.15.4.1 |
TX requirements (Power class) |
|
R4-2205582 |
On configured output power for NR SL inter-band con-current operation |
Huawei, HiSilicon |
R4-2206332 |
Email discussion summary for [102-e][132] NRSL_enh_Part_3 |
Moderator (Huawei) |
R4-2206432 |
Email discussion summary for [102-e][132] NRSL_enh_Part_3 |
Moderator (Huawei) |
10.15.4.2 |
Coexistence study |
|
R4-2205134 |
TP to TR 38.785 on the co-channel co-existence issue |
Xiaomi |
R4-2205538 |
Tp for Co-channel existing |
Ericsson |
R4-2206532 |
TP to TR 38.785 on the co-channel co-existence issue |
Xiaomi |
10.15.5 |
RRM core requirements |
|
R4-2203718 |
On NR SL RRM Core Requirement |
Qualcomm, Inc. |
R4-2204147 |
Big CRs : RRM requirements for Rel-17 NR SL enhancement |
LG Electronics |
R4-2206766 |
Email discussion summary for [102-e][223] NR_SL_enh_RRM |
Moderator (LGE) |
R4-2206916 |
WF on NR SL enhancements RRM requirements |
LGE |
R4-2206917 |
draft CR on interruption requirement for SL |
LG Electronics |
R4-2207064 |
Email discussion summary for [102-e][223] NR_SL_enh_RRM |
Moderator (LGE) |
10.15.5.1 |
Intra-band con-current V2X operation |
|
R4-2203906 |
Discussion on remaining issues for intra-band con-current SL operation |
CATT |
R4-2204244 |
Further discussion on RRM requirements for intra-band con-current V2X operation |
Xiaomi |
R4-2204298 |
Discussion on RRM impact of intra-band concurrent V2X operation |
OPPO |
R4-2204644 |
Remaining issues on Intra-band con-current V2X operation RRM requirements |
vivo |
R4-2205640 |
Discussions on interruptions due to SL DRX for Rel-17 SL operation |
Ericsson |
10.15.5.2 |
SL-DRX |
|
R4-2203907 |
Discussion on remaining issues for RRM requirements related to SL-DRX |
CATT |
R4-2204145 |
RRM requirements for SL-DRX |
LG Electronics |
R4-2204245 |
Further discussion on RRM requirements related to SL-DRX |
Xiaomi |
R4-2204299 |
Discussion on SL-DRX |
OPPO |
R4-2204645 |
Remaining issues on SL-DRX RRM requirements |
vivo |
R4-2205333 |
Discussion on RRM remaining issues related to SL-DRX |
Huawei, HiSilicon |
R4-2205401 |
Discussions on DRX in NR SL enhancement |
ZTE Corporation |
R4-2205641 |
Draft CR on WAN interruptions due to SL DRX for Rel-17 SL enhancement in TS 38.133 |
Ericsson |
10.15.5.3 |
Others |
|
R4-2204146 |
draft CR on interruption requirement for SL |
LG Electronics |
R4-2204646 |
Draft CR on Selection Reselction of V2X Synchronization Reference Source for sidelink enhancement |
vivo |
R4-2206918 |
Draft CR on Selection Reselction of V2X Synchronization Reference Source for sidelink enhancement |
vivo |
10.15.6 |
RRM performance requirements |
|
R4-2203719 |
On NR SL RRM Performance Requirement Scope |
Qualcomm, Inc. |
R4-2203908 |
Discussion on RRM test cases for sidelink operation |
CATT |
R4-2204148 |
Work Plan and Test Case List for NR SL enh RRM performance |
LG Electronics |
10.15.7 |
Demodulation performance requirements |
|
R4-2204317 |
Work plan and scope for NR sidelink enhancement demodulation performance |
LG Electronics Inc. |
R4-2205801 |
Discussions on Rel-17 sidelink UE requirements |
Huawei,HiSilicon |
R4-2207171 |
Email discussion summary for [102-e][332] NR_SL_enh_Demod_NWM |
Moderator (LGE) |
R4-2207224 |
WF on SL enhancement demodulation |
LGE |
R4-2207444 |
Email discussion summary for [102-e][332] NR_SL_enh_Demod_NWM |
Moderator (LGE) |
10.16 |
Extending current NR operation to 71GHz |
|
R4-2205190 |
Reply LS on the minimum guard period between two SRS resources for antenna switching |
Huawei, HiSilicon |
R4-2206587 |
draft CR on vehicular UE Tx RF requirements in FR2-2 |
LG Electronics Finland |
R4-2206588 |
draft CR on vehicular UE Rx RF requirements in FR2-2 |
LG Electronics Finland |
10.16.1 |
General |
|
R4-2203581 |
Draft LS on sensing beam characteristics to RAN1 |
Ericsson |
R4-2203807 |
On sensing beam selection on the UE side |
Apple |
R4-2203937 |
Draft reply LS on sensing beam selection |
CATT |
R4-2203941 |
Draft reply LS on the minimum guard period between two SRS resources for antenna switching |
CATT |
R4-2204932 |
Draft CR for TS 38.101-2: Introduction of system parameters for FR2-2 |
vivo |
R4-2205129 |
Discussion and draft reply LS on minimum guard symbol of SRS |
Xiaomi |
R4-2205732 |
Views on sensing beam selection on the UE side |
Sony |
R4-2205997 |
UE feature list for NR ext. to 71GHz |
Intel Corporation |
R4-2206048 |
SRS antenna switching in FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2206333 |
Email discussion summary for [102-e][133] NR_ext_to_71GHz_Part_1 |
Moderator (Intel) |
R4-2206433 |
Email discussion summary for [102-e][133] NR_ext_to_71GHz_Part_1 |
Moderator (Intel) |
R4-2206533 |
LS to RAN1 on sensing beam characteristics |
Ericsson |
R4-2206534 |
Draft reply LS on the minimum guard period between two SRS resources for antenna switching |
CATT |
R4-2206535 |
WF on system parameters of FR2-2 |
Intel Corporation |
R4-2206607 |
Draft CR to TS 38.101-2: Channel arrangement |
Ericsson |
10.16.2 |
Operation bands and system parameters (channelization, raster, CBW, etc) |
|
R4-2203805 |
Remaining issues on system parameters for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2203936 |
ON channelization and sync raster entries for up to 71GHz |
CATT |
R4-2204933 |
Further discussion on channel raster and sync raster for 52.6~71 GHz |
vivo |
R4-2205020 |
Draft CR to TS 38.104: Channel arrangement |
Ericsson |
R4-2205021 |
Draft CR to TS 38.101-2: Channel arrangement |
Ericsson |
R4-2205022 |
52.6-71 GHz System Parameters |
Ericsson |
R4-2205233 |
60GHz channel and synchronization raster |
LG Electronics Finland |
R4-2205313 |
System parameters for a NR band in the range 52.6GHz – 71GHz |
Nokia, Nokia Shanghai Bell |
R4-2205315 |
60 GHz system parameters |
Qualcomm Incorporated |
R4-2205988 |
Further discussion on the channel raster and sync raster in FR2-2 |
Huawei, HiSilicon |
R4-2205998 |
Views on FR2-2 channelization |
Intel Corporation |
R4-2206582 |
Draft CR to TS 38.104: Channel arrangement |
Ericsson |
R4-2206583 |
Draft CR to TS 38.101-2: Channel arrangement |
Ericsson |
10.16.3 |
UE RF requirements |
|
R4-2203707 |
On UE spherical coverage for band n263 |
Apple |
R4-2204330 |
Specifications of FR2-2 handheld UE |
Murata Manufacturing Co Ltd. |
R4-2206334 |
Email discussion summary for [102-e][134] NR_ext_to_71GHz_Part_2 |
Moderator (Qualcomm) |
R4-2206434 |
Email discussion summary for [102-e][134] NR_ext_to_71GHz_Part_2 |
Moderator (Qualcomm) |
R4-2206536 |
WF on 60 GHz UE RF |
Qualcomm |
10.16.3.1 |
TX requirements |
|
R4-2204038 |
Minimum Tx requirement for handheld and FWA UEs at 60 GHz |
Sony |
R4-2204227 |
Proposals on FR2-2 spherical drop for requirement calculation |
MediaTek Beijing Inc. |
R4-2204359 |
Handheld UE RF TX requirements for n263 in FR2-2 |
NTT DOCOMO, INC. |
R4-2204590 |
Views on FR2-2 FWA UE |
Murata Manufacturing Co Ltd. |
R4-2204619 |
UE output power for 57-71 GHz |
Ericsson |
R4-2204934 |
Further discussion on handheld UE EIRP and spherical coverage requirements for 52.6~71 GHz |
vivo |
R4-2205173 |
Draft CR to 38.101-2 on band n263 Tx aspects |
Apple |
R4-2205188 |
On 60GHz UE Tx RF requirements |
Huawei, HiSilicon |
R4-2205210 |
draft CR on vehicular UE Tx RF requirements in FR2-2 |
LG Electronics Finland |
R4-2205227 |
Discussion on Tx RF requirements in FR2-2 |
LG Electronics Finland |
R4-2205246 |
60 GHz UE TX |
Qualcomm Incorporated |
R4-2205459 |
Further Discussion on spectral utilization requirements for FR2-2 |
ZTE Corporation |
R4-2205552 |
On UE Tx RF aspects for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2205999 |
UE Tx RF requirements for FR2-2 |
Intel Corporation |
10.16.3.2 |
RX requirements |
|
R4-2204039 |
Minimum Rx requirement for handheld UEs at 60 GHz |
Sony |
R4-2204360 |
Handheld UE RF RX requirements for n263 in FR2-2 |
NTT DOCOMO, INC. |
R4-2204935 |
Further discussion on handheld UE EIS requirements for 52.6~71 GHz |
vivo |
R4-2205189 |
On 60GHz UE Rx RF requirements |
Huawei, HiSilicon |
R4-2205229 |
draft CR on vehicular UE Rx RF requirements in FR2-2 |
LG Electronics Finland |
R4-2205231 |
Discussion on Rx RF requirements in FR2-2 |
LG Electronics Finland |
R4-2205292 |
60 GHz UE RX |
Qualcomm Incoprorated |
R4-2205553 |
On UE Rx RF aspects for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2206000 |
UE EIS requirements for band n263 |
Intel Corporation |
10.16.4 |
BS RF requirements |
|
R4-2207216 |
WF on >52.6 GHz BS RF Tx Requirements |
Nokia, Nokia Shanghai Bell |
R4-2207511 |
Big CR to 38.104 for Rel-17 NR extension up to 71 GHz introduction |
Nokia |
10.16.4.1 |
TX requirements |
|
R4-2203577 |
On BS RF transmitter requirements for the frequency range 52 to 71 GHz |
Ericsson |
R4-2203579 |
Draft CR to TS 38.104: Addition of requirements for NR extension up to 71 GHz in subclause 9.6 to 9.8 |
Ericsson |
R4-2203649 |
Proposals on BS transmitter requirements for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2203650 |
Draft CR to TR 38.104: Clauses 9.1 to 9.5 |
Nokia, Nokia Shanghai Bell |
R4-2203975 |
Discussion on BS TX RF requirements for 52 6-71GHz |
CATT |
R4-2204436 |
Discussion on BS RF Tx requirements for 52.6 – 71 GHz |
NEC |
R4-2205460 |
Further discussion on BS Tx requirements for 52.6-71GHz |
ZTE Corporation |
R4-2206119 |
Discussion on the remaining BS RF requirements for FR2-2: Tx requirements |
Huawei, HiSilicon |
R4-2207172 |
Email discussion summary for [102-e][312] NR_exto71GHz_BSRF |
Moderator (Nokia) |
R4-2207217 |
WF on >52.6 GHz BS RF Rx Requirements |
Ericsson |
R4-2207218 |
WF on >52.6 GHz BS RF conformance aspects |
Keysight Technologies UK Ltd |
R4-2207220 |
Draft CR to TS 38.104: Addition of requirements for NR extension up to 71 GHz in subclause 9.6 to 9.8 |
Ericsson |
R4-2207221 |
Draft CR to TR 38.104: Clauses 9.1 to 9.5 |
Nokia, Nokia Shanghai Bell |
R4-2207445 |
Email discussion summary for [102-e][312] NR_exto71GHz_BSRF |
Moderator (Nokia) |
10.16.4.2 |
RX requirements |
|
R4-2203578 |
On BS RF receiver requirements for the frequency range 52 to 71 GHz |
Ericsson |
R4-2203651 |
Proposals on BS receiver requirements for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2203976 |
Discussion on BS RX RF requirements for 52 6-71GHz |
CATT |
R4-2205461 |
Further discussion on BS Rx requirements for 52.6-71GHz |
ZTE Corporation |
R4-2205462 |
Draft CR for TS 38.104 on introduction of BS RF Rx requirements for 57-71GHz in section 10.6 – 10.9 |
ZTE Corporation |
R4-2206120 |
Discussion on the remaining BS RF requirements for FR2-2: Rx requirements |
Huawei, HiSilicon |
R4-2207222 |
Draft CR for TS 38.104 on introduction of BS RF Rx requirements for 57-71GHz in section 10.6 – 10.9 |
ZTE Corporation |
10.16.5 |
BS RF conformance testing |
|
R4-2203582 |
Initial considerations related to BS RF conformance testing and NR extension up to 71 GHz |
Ericsson |
R4-2203652 |
This contribution provides proposals on BS RF conformance testing requirements for extending current NR operation to 71 GHz, focusing on test complexity with the shorter slot durations for the larger 480 kHz SCS and 960 kHz SCS |
Nokia, Nokia Shanghai Bell |
R4-2204712 |
about FR2-2 BS conformance test system MU |
Keysight Technologies UK Ltd |
R4-2205668 |
Discussion on limitation of the measurement interval for the determination of the averaged EVM for FR2-2, test time improvements and possible impact on measuring uncertainties (minimal) |
ROHDE & SCHWARZ, KEYSIGHT |
10.16.7 |
FR1+FR2-2 DC/CA band combinations |
|
R4-2206053 |
CR for 38.101-3 on FR2-2 DC/CA with FR1 anchor |
Ericsson GmbH, Eurolab |
10.16.8 |
RRM core requirements |
|
R4-2206927 |
DraftCR for FR2-2 LBT support in Intra-Frequency measurements |
Nokia, Nokia Shanghai Bell |
10.16.8.1 |
General |
|
R4-2203531 |
Discussion on general RRM requirements for extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2203889 |
Further discussion on general RRM requirements for extension to 71GHz |
CATT |
R4-2204188 |
Discussion on RRM requirements in FR2-2 |
MediaTek inc. |
R4-2204189 |
Scheduling restriction due to L3 measurements for FR2-2 |
MediaTek inc. |
R4-2204190 |
Scheduling restriction due to L1 measurements for FR2-2 |
MediaTek inc. |
R4-2204315 |
Discussion on general RRM measurement requirements for extension to 71GHz |
LG Electronics Inc. |
R4-2204636 |
Further discussion on RRM impacts for extending NR operation to 71GHz |
vivo |
R4-2204726 |
General RRM requirements for extending NR operation to 71GHz |
Ericsson |
R4-2204728 |
draftCR on cell reselection in Idle mode for FR2-2 CCA |
Ericsson |
R4-2204874 |
Discussion on general RRM impacts for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2206767 |
Email discussion summary for [102-e][224] NR_ext_to_71GHz_RRM_1 |
Moderator (Qualcomm) |
R4-2206919 |
WF on NR extension to 71 GHz RRM requirements (Part 1) |
Qualcomm |
R4-2206921 |
Scheduling restriction due to L3 measurements for FR2-2 |
MediaTek inc. |
R4-2206922 |
Scheduling restriction due to L1 measurements for FR2-2 |
MediaTek inc. |
R4-2207065 |
Email discussion summary for [102-e][224] NR_ext_to_71GHz_RRM_1 |
Moderator (Qualcomm) |
R4-2207122 |
Big CR: RRM requirements for Rel-17 NR extension to 71GHz |
Intel Corporation, Qualcomm |
10.16.8.2 |
Timing requirements |
|
R4-2203532 |
Discussion on RRM timing requirements for extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2203533 |
Draft CR adding timing requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2203806 |
UE transmit timing for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2203890 |
Further discussion on RRM timing requirements for higher SCS |
CATT |
R4-2204191 |
Discussion on timing requirements in FR2-2 |
MediaTek inc. |
R4-2204635 |
Further discussion on timing for 52.6-71GHz |
vivo |
R4-2204875 |
Discussion on timing requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2205403 |
On Te requirements for NR systems extended to 71 GHz |
ZTE Corporation |
R4-2205417 |
UE Timing requirements |
Ericsson |
R4-2206005 |
Discussion on timing requirements for NR 52.6 – 71 GHz |
Intel Corporation |
R4-2206115 |
Timing requirements in FR2-2 |
Qualcomm Incorporated |
R4-2206923 |
Draft CR adding timing requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
10.16.8.3 |
Interruption requirements |
|
R4-2204876 |
Discussion on interruption requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2204877 |
Draft CR on interruption requirements for FR2-2 |
Huawei, Hisilicon |
R4-2206768 |
Email discussion summary for [102-e][225] NR_ext_to_71GHz_RRM_2 |
Moderator (Intel) |
R4-2206924 |
WF on NR extension to 71 GHz RRM requirements (Part 2) |
Intel |
R4-2207066 |
Email discussion summary for [102-e][225] NR_ext_to_71GHz_RRM_2 |
Moderator (Intel) |
10.16.8.4 |
Active BWP switching delay requirements |
|
R4-2204541 |
Draft CR - Correction on BWP switch delay for dormant BWP in FR2-2 |
Nokia, Nokia Shanghai Bell |
10.16.8.6 |
LBT impacts on RRM requirements |
|
R4-2203808 |
LBT impacts on RRM requirements for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2204192 |
Discussion on LBT impacts on RRM requirements in FR2-2 |
MediaTek inc. |
R4-2204193 |
Introduction of SCell activation with CCA for FR2-2 |
MediaTek inc. |
R4-2204194 |
Introduction of TCI state switch with CCA for FR2-2 |
MediaTek inc. |
R4-2204542 |
DraftCR: FR2-2 LBT support in Intra-Frequency measurements |
Nokia, Nokia Shanghai Bell |
R4-2204543 |
LBT impact on NR RRM requirements in FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2204634 |
Draft CR for FR2-2 LBT support in requirements for PSCell addition and release delay, PSCell change and Conditional PSCell change |
vivo |
R4-2204650 |
Further discussion on LBT requirements for FR2-2 |
vivo |
R4-2204727 |
LBT requirements for 71GHz |
Ericsson |
R4-2204878 |
Discussion on LBT impacts for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2204879 |
Draft CR on RLM and Link recovery procedures for unlicensed operation in FR2-2 |
Huawei, Hisilicon |
R4-2205404 |
On LBT impacts on RRM for NR systems extended to 71 GHz |
ZTE Corporation |
R4-2206006 |
Discussion on LBT impacts on RRM requirements for NR 52.6 – 71 GHz |
Intel Corporation |
R4-2206007 |
DraftCR for FR2-2 LBT support in RRC_IDLE and RRC_CONNECTED state mobility requirements |
Intel Corporation |
R4-2206840 |
Introduction of SCell activation delay requirement for FR2 inter-band CA with common beam management |
MediaTek inc. |
R4-2206925 |
Introduction of SCell activation with CCA for FR2-2 |
MediaTek inc. |
R4-2206926 |
introduction of TCI state switch with CCA for FR2-2 |
MediaTek inc. |
R4-2206928 |
Draft CR for FR2-2 LBT support in requirements for PSCell addition and release delay, PSCell change and Conditional PSCell change |
vivo |
R4-2206930 |
Draft CR on RLM and link recovery requirements for FR2-2 unlicensed operation |
Huawei, Hisilicon |
R4-2206931 |
DraftCR for FR2-2 LBT support in RRC_IDLE and RRC_CONNECTED state mobility requirements |
Intel Corporation |
R4-2206946 |
Draft CR for Introduction of DL TCI state switching delay for unified TCI |
ZTE Corporation |
R4-2206947 |
Draft CR for Introduction of DL TCI state switching delay for unified TCI |
ZTE Corporation |
R4-2207018 |
Draft CR for implement new parameter measCyclePSCell for measurement on deactivated SCG |
Ericsson |
10.16.9 |
Others |
|
R4-2203938 |
Discussion on the FR2-2 LBT requirement |
CATT |
R4-2203939 |
Draft CR for TS 37.106: introduction of UE LBT requirement for FR2-2 |
CATT |
R4-2203940 |
Draft CR for TS 37.107: introduction of BS LBT requirement for FR2-2 |
CATT |
R4-2204620 |
Reply LS on a minimum guard period between two SRS resources for antenna switching |
Ericsson |
R4-2204936 |
Discussion and draft reply LS on sensing beam selection |
vivo |
R4-2206047 |
Sensing beam for LBT in FR2-2 |
Nokia, Nokia Shanghai Bell |
10.16.10.1 |
General |
|
R4-2203530 |
Discussion on general demodulation requirements for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2204031 |
Discussion on general issue of NR extended to 71GHz demodulation |
Ericsson |
R4-2204589 |
Discussion on BS demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2205916 |
Work management for FR2-2 demodulation performance requirement definition |
Intel Corporation |
R4-2205917 |
General views on FR2-2 demodulation performance requirements |
Intel Corporation |
R4-2207173 |
Email discussion summary for [102-e][327] NR_exto71GHz_Demod_NWM |
Moderator (Intel) |
R4-2207205 |
Work management for FR2-2 demodulation performance requirement definition |
Intel Corporation |
R4-2207223 |
WF on demodulation performance requirements definition for 52.6 - 71 GHz |
Intel Corporation |
R4-2207446 |
Email discussion summary for [102-e][327] NR_exto71GHz_Demod_NWM |
Moderator (Intel) |
10.16.10.2 |
UE Demodulation and CSI requirements |
|
R4-2204584 |
UE demodulation and CSI reporting requirements for FR2-2 |
Ericsson |
R4-2204834 |
On ext_to_71GHz UE Demodulation and CSI requirements |
Nokia, Nokia Shanghai Bell |
R4-2205802 |
Discussions on UE requirements for NR extension to 71GHz |
Huawei,HiSilicon |
R4-2205918 |
View on FR2-2 UE demodulation performance requirements |
Intel Corporation |
10.16.10.3 |
BS demodulation requirements |
|
R4-2204032 |
Discussion on f NR extended to 71GHz BS demodulation |
Ericsson |
R4-2204395 |
View on FR2-2 BS demodulation performance requirements |
Intel Corporation |
R4-2205803 |
Discussions on BS requirements for NR extension to 71GHz |
Huawei,HiSilicon |
10.17.1 |
General |
|
R4-2204583 |
Big CR to TS38.174 for Rel-17 IAB enhancement |
Samsung |
R4-2207174 |
Email discussion summary for [102-e][313] NR_eIAB_RF |
Moderator (Samsung) |
R4-2207212 |
WF on candidate issues for NR eIAB conformance testing |
Samsung |
R4-2207447 |
Email discussion summary for [102-e][313] NR_eIAB_RF |
Moderator (Samsung) |
10.17.2.1 |
Impact for Simultaneous operation of IAB child and parent links |
|
R4-2204434 |
Draft CR for RF requirements due to Tx power imbalance between IAB-MT and IAB-DU |
ZTE Corporation |
R4-2204579 |
Draft CR to 38.174: update to general clause for R17 enhancement |
Samsung |
R4-2206043 |
DraftCR to TS 38.174: Introduction of conducted transmitter requirements for eIAB |
Nokia, Nokia Shanghai Bell |
R4-2207213 |
Draft CR for RF requirements due to Tx power imbalance between IAB-MT and IAB-DU |
ZTE Corporation |
R4-2207214 |
Draft CR to 38.174: update to general clause for R17 enhancement |
Samsung |
10.17.2.2 |
Impact for Timing enhancement |
|
R4-2204433 |
Discussion on timing issues for simultaneous operation of IAB |
ZTE Corporation |
R4-2204580 |
Timing enhancement on Rel-17 IAB |
Samsung |
R4-2205527 |
IAB MT /DU case 6 timing |
Ericsson |
R4-2205975 |
eIAB – case#6 intra node TAE |
Huawei |
R4-2206044 |
Discussion on timing error for eIAB |
Nokia, Nokia Shanghai Bell |
10.17.3 |
RF conformance testing |
|
R4-2203592 |
On RRM for eIAB |
ZTE Corporation |
R4-2204581 |
Initial discussion on Rel-17 IAB enhancement on RF conformance testing |
Samsung |
R4-2205202 |
Discussion on eIAB performance works |
Nokia, Nokia Shanghai Bell |
R4-2205526 |
IAB conformance testing aspects |
Ericsson |
10.17.4 |
RRM core requirements |
|
R4-2203642 |
CLI measurement requirement for R17 NR eIAB RRM |
Qualcomm CDMA Technologies |
R4-2204880 |
Discussion on RRM requirements for eIAB |
Huawei, Hisilicon |
R4-2204881 |
CR on timing requirements for Rel-17 IAB |
Huawei, Hisilicon |
R4-2205410 |
On RRM for eIAB |
ZTE Corporation |
R4-2205962 |
On IAB Enhanced RRM Requirements |
Nokia, Nokia Shanghai Bell |
R4-2206029 |
Further analysis of RRM requirements for enhanced IAB |
Ericsson |
R4-2206030 |
Case 6 timing requirement for IAB in TS 38.174 |
Ericsson |
R4-2206769 |
Email discussion summary for [102-e][226] NR_IAB_enh_RRM |
Moderator (ZTE) |
R4-2206932 |
WF on IAB enhancement RRM |
ZTE Corporation |
R4-2206933 |
Case 6 timing requirement for IAB in TS 38.174 |
Ericsson |
R4-2207067 |
Email discussion summary for [102-e][226] NR_IAB_enh_RRM |
Moderator (ZTE) |
10.17.5 |
Demodulation requirements |
|
R4-2204582 |
Initial discussion on demodulation aspect for Rel-17 IAB enhancement |
Samsung |
R4-2205032 |
eIAB demodulation requirements |
Ericsson |
R4-2205771 |
Discussion on eIAB demod |
Huawei,HiSilicon |
R4-2205966 |
On IAB Enhanced Demodulation Performance Requirements |
Nokia, Nokia Shanghai Bell |
R4-2207175 |
Email discussion summary for [102-e][328] NR_eIAB_Demod_NWM |
Moderator (Nokia, Nokia Shanghai Bell) |
R4-2207199 |
WF on specification of Rel-17 NR_IAB_enh demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2207448 |
Email discussion summary for [102-e][328] NR_eIAB_Demod_NWM |
Moderator (Nokia, Nokia Shanghai Bell) |
10.18.1 |
General and CR structure |
|
R4-2203818 |
Updated RAN4 RF work plan for NR coverage enhancements WI |
China Telecom |
R4-2203822 |
38.101-1 CR: UE RF requirements for DMRS bundling |
China Telecom |
R4-2203823 |
38.101-2 CR: UE RF requirements for DMRS bundling |
China Telecom |
R4-2204820 |
Draft CR on UE RF requirements for DMRS bundling |
Huawei, HiSilicon |
R4-2204821 |
Draft CR on UE RF requirements for DMRS bundling |
Huawei, HiSilicon |
R4-2205531 |
simulation updated results for phase tolerance for PUSCH repetition |
Ericsson |
R4-2205532 |
LS reply on DMRS bundling for PUSCH and PUCCH |
Ericsson |
R4-2206336 |
Email discussion summary for [102-e][136] NR_cov_enh |
Moderator (China Telecom) |
R4-2206436 |
Email discussion summary for [102-e][136] NR_cov_enh |
Moderator (China Telecom) |
R4-2206537 |
Reply LS on Maximum duration for DMRS bundling |
Qualcomm Incorporated |
R4-2206538 |
CR on UE RF requirements for DMRS bundling in TS 38.101-1 |
Huawei, HiSilicon |
R4-2206539 |
CR on UE RF requirements for DMRS bundling in TS 38.101-2 |
Huawei, HiSilicon |
R4-2206540 |
WF on issues for maintenance of NR coverage enhancements |
Ericsson |
R4-2206580 |
Reply LS on Length of Maximum duration |
Qualcomm Incorporated |
R4-2206593 |
WF on issues for maintenance of NR coverage enhancements |
Main Session |
R4-2206632 |
CR on measurement for DMRS bundling in TS 38.101-1 |
Ericsson |
R4-2206633 |
CR on measurement for DMRS bundling in TS 38.101-2 |
Ericsson |
R4-2206640 |
CR on measurement for DMRS bundling in TS 38.101-1 |
Ericsson |
R4-2206641 |
CR on measurement for DMRS bundling in TS 38.101-2 |
Ericsson |
10.18.2 |
UE RF requirements |
|
R4-2206131 |
Coverage enhancements – remaining UE RF requirements aspects |
MediaTek (Chengdu) Inc. |
10.18.2.1 |
Requirements for non-scheduled gap |
|
R4-2203819 |
Non-zero un-scheduled gap in between PUSCH/PUCCH transmissions |
China Telecom |
R4-2205530 |
RF impact on non-scheduled gap |
Ericsson |
10.18.2.2 |
Tolerance for power consistency/phase continuity |
|
R4-2203820 |
On phase continuity tolerance for DMRS bundling |
China Telecom |
R4-2205529 |
On JCE phase continuity and power consistency tolerance for PUCCH and PUSCH |
Ericsson |
R4-2205535 |
CR on phase tolerance for DMRS bundling in TS 38.101-1 |
Ericsson |
R4-2205536 |
CR on phase tolerance for DMRS bundling in TS 38.101-2 |
Ericsson |
R4-2205882 |
Discussion on UE phase discontinuity requirement |
Qualcomm Incorporated |
R4-2206014 |
On phase continuity requirement with coverage enhancement |
Apple |
10.18.2.3 |
Maximum duration for joint channel estimation |
|
R4-2203821 |
On maximum duration for DMRS bundling |
China Telecom |
R4-2204818 |
On phase continuity for multiple transmissions |
Huawei, HiSilicon |
R4-2205537 |
LS reply On maximum duration of phase continuity and power consistency for PUCCH and PUSCH repetition |
Ericsson |
10.18.2.4 |
Others |
|
R4-2204819 |
On maximum length for the non-zero un-scheduled gap |
Huawei, HiSilicon |
R4-2205528 |
On measurement of the TX coherent transmission |
Ericsson |
R4-2205533 |
CR on measurment for DMRS bundling in TS 38.101-1 |
Ericsson |
R4-2205534 |
CR on measurment for DMRS bundling in TS 38.101-2 |
Ericsson |
R4-2206541 |
CR on measurment for DMRS bundling in TS 38.101-1 |
Ericsson |
R4-2206542 |
CR on measurment for DMRS bundling in TS 38.101-2 |
Ericsson |
10.18.3 |
BS demodulation requirements |
|
R4-2206132 |
JCE BS demodulation requirements |
MediaTek (Chengdu) Inc. |
R4-2207210 |
WF on PUSCH demodulation performance of Rel-17 NR coverage enhancement |
China Telecom |
R4-2207211 |
WF on PUCCH demodulation performance of Rel-17 NR coverage enhancement |
Nokia |
10.18.3.1 |
PUSCH requirements |
|
R4-2203552 |
View on PUSCH demodulation requirement for Rel-17 coverage enhancement |
Samsung |
R4-2204033 |
Discussion on NR coverage enhancement PUSCH demodulation |
Ericsson |
R4-2205489 |
PUSCH demodulation performance of Rel-17 NR coverage enhancements |
Nokia, Nokia Shanghai Bell |
R4-2205500 |
On BS PUSCH demodulation requirements for NR coverage enhancements |
China Telecom |
R4-2205772 |
Discussion on BS coverage enhancement demod PUSCH |
Huawei,HiSilicon |
R4-2205817 |
Discussion on PUSCH demodulation requirements for NR coverage enhancements WI |
Intel Corporation |
R4-2207176 |
Email discussion summary for [102-e][329] NR_cov_enh_Demod |
Moderator (China Telecom) |
R4-2207449 |
Email discussion summary for [102-e][329] NR_cov_enh_Demod |
Moderator (China Telecom) |
10.18.3.2 |
PUCCH requirements |
|
R4-2203553 |
View on PUCCH demodulation requirement for Rel-17 coverage enhancement |
Samsung |
R4-2204034 |
Discussion on NR coverage enhancement PUCCH demodulation |
Ericsson |
R4-2205490 |
PUCCH demodulation performance of Rel-17 NR coverage enhancements |
Nokia, Nokia Shanghai Bell |
R4-2205501 |
On BS PUCCH demodulation requirements for NR coverage enhancements |
China Telecom |
R4-2205773 |
Discussion on BS coverage enhancement demod PUCCH |
Huawei,HiSilicon |
R4-2205818 |
Discussion on PUCCH demodulation requirements for NR coverage enhancements WI |
Intel Corporation |
10.19.1 |
General |
|
R4-2203772 |
Discussion on Impact to RF and RRM requirements with simultaneous reception |
Apple |
R4-2204402 |
Discussion on simultaneous reception in FeMIMO |
Intel Corporation |
R4-2204519 |
Requirements for Simultaneous Reception in FR2 |
Qualcomm Incorporated |
R4-2204730 |
Multi-panel simultaneous reception of FeMIMO |
Samsung |
R4-2205842 |
Discussion on Simultaneous reception with different QCL-type D |
Ericsson |
R4-2206337 |
Email discussion summary for [102-e][137] NR_feMIMO |
Moderator (Samsung) |
R4-2206437 |
Email discussion summary for [102-e][137] NR_feMIMO |
Moderator (Samsung) |
R4-2206543 |
WF on RF impact of FeMIMO |
Samsung |
R4-2206603 |
WF on RF impact of FeMIMO |
Samsung |
10.19.2.1 |
Additional requirement for multi-panel reception |
|
R4-2203703 |
Multi-panel FR2 UE requirements |
Apple |
R4-2204224 |
Rationality on potential additional FR2 FeMIMO multi-panel reception requirement |
MediaTek Beijing Inc. |
R4-2204971 |
Further discussion on impact of multi-panel reception requirements |
vivo |
R4-2205014 |
Discussion on Additional requirement for multi-panel reception |
ZTE Corporation |
R4-2205103 |
RF Requirements for Multi-panel in FR2 |
Qualcomm Incorporated |
10.19.2.2 |
Impact of MPE enhancements |
|
R4-2204972 |
Further discussion on impact of MPE requirements |
vivo |
R4-2205015 |
Discussion on Impact of MPE enhancements |
ZTE Corporation |
R4-2205609 |
Requirements for MPE mitigation |
Nokia, Nokia Shanghai Bell |
R4-2205658 |
On the impact of per-beam based PMPR reporting |
Apple |
10.19.2.3 |
SRS related impact |
|
R4-2204621 |
SRS time masks for SRS usage set to antenna switching for FeMIMO |
Ericsson |
R4-2204824 |
Remaining issues for SRS |
Huawei, HiSilicon |
R4-2205142 |
Handling of GP in GAP between two different SRS resource sets |
Nokia, Nokia Shanghai Bell |
10.19.3 |
RRM core requirements |
|
R4-2206934 |
WF on FeMIMO RRM requirements for inter-cell beam management |
Samsung |
R4-2206935 |
WF on other RRM requirements for FeMIMO |
Huawei |
R4-2206936 |
ReplyLS on L1-RSRP measurement behaviour when SSBs associated with different PCIs overlap |
Vivo |
R4-2207108 |
WF on FeMIMO RRM requirements for inter-cell beam management |
Samsung |
R4-2207123 |
Big CR: RRM requirements for Rel-17 NR feMIMO |
Samsung |
10.19.3.1 |
Unified TCI for DL and UL |
|
R4-2203773 |
Discussion on RRM requirements for Unified TCI |
Apple |
R4-2204266 |
Discussion on unified TCI |
CMCC |
R4-2204270 |
Unified TCI in FeMIMO |
BEIJING SAMSUNG TELECOM R&D |
R4-2204339 |
Discussion on RRM requirements for unified TCI in R17 feMIMO |
vivo |
R4-2204340 |
draft CR on active DL and UL TCI state list update delay in R17 |
vivo |
R4-2204365 |
Discussion on unified TCI for DL and UL in R17 feMIMO |
MediaTek Inc. |
R4-2204396 |
Discussion on Unified TCI state in FeMIMO |
Intel Corporation |
R4-2204403 |
DraftCR to TS 38.133: MAC-CE based downlink/uplink TCI state switch delay for unified TCI state |
Intel Corporation |
R4-2204491 |
Draft CR for Introduction of DL TCI state swithcing delay for unified TCI |
ZTE Corporation |
R4-2204492 |
Draft CR for Introduction of UL TCI state swithcing delay for unified TCI |
ZTE Corporation |
R4-2205016 |
Discussion on Unified TCI for DL and UL |
ZTE Corporation |
R4-2205039 |
Discussion on requirements of unified TCI for DL and UL |
Nokia, Nokia Shanghai Bell |
R4-2205042 |
DraftCR on DCI based DL and UL TCI switching delay requirements |
Nokia, Nokia Shanghai Bell |
R4-2205334 |
Discussion on TCI state switching delay requirements for R17 unified TCI |
Huawei, HiSilicon |
R4-2205335 |
DraftCR on known condition requirements for R17 unified TCI |
Huawei, HiSilicon |
R4-2205843 |
RRM requirements of unified TCI state for FeMIMO |
Ericsson |
R4-2206783 |
Email discussion summary for [102-e][240] NR_feMIMO_RRM_2 |
Moderator (Intel) |
R4-2206943 |
WF on FeMIMO RRM impact for unified TCI state |
Intel |
R4-2206944 |
draft CR on active DL and UL TCI state list update delay requirements in R17 |
vivo |
R4-2206945 |
DraftCR to TS 38.133: MAC-CE based downlink/uplink TCI state switch delay for unified TCI state |
Intel Corporation |
R4-2206948 |
DraftCR on DCI based DL and UL TCI switching delay requirements |
Nokia, Nokia Shanghai Bell |
R4-2206949 |
DraftCR on known condition requirements for R17 unified TCI |
Huawei, HiSilicon |
R4-2207015 |
DraftCR on L1/L3 measurement requirements for deactivated SCG |
vivo |
R4-2207081 |
Email discussion summary for [102-e][240] NR_feMIMO_RRM_2 |
Moderator (Intel) |
R4-2207097 |
DraftCR on DCI based DL and UL TCI switching delay requirements |
Xiaomi |
10.19.3.2 |
Inter-cell beam management |
|
R4-2203774 |
Discussion on RRM requirements for inter-cell beam management |
Apple |
R4-2203775 |
Draft CR on Inter-cell L1-RSRP measurements |
Apple |
R4-2204267 |
Discussion on inter-cell beam management |
CMCC |
R4-2204341 |
Discussion on RRM requirements for inter-cell L1 beam measurements in R17 feMIMO |
vivo |
R4-2204342 |
draft CR on L1-RSRP measurement requirements for inter-cell BM in R17 |
vivo |
R4-2204366 |
Discussion on inter cell beam management in R17 feMIMO |
MediaTek Inc. |
R4-2204368 |
CR for measurement restriction and scheduling availability for inter cell L1-RSRP measurement in R17 |
MediaTek Inc. |
R4-2204397 |
Discussion on inter-cell beam management in FeMIMO |
Intel Corporation |
R4-2204517 |
Requirements for Inter-Cell Beam Management |
Qualcomm Incorporated |
R4-2204696 |
DraftCR on Introduction of L1-RSRP measurements on NSC for Rel-17 FeMIMO |
Samsung |
R4-2204697 |
Discussion on UE behaviour for SSB-based L1 measurement on NSC |
Samsung |
R4-2204698 |
RRM requirement for inter-cell beam management in FeMIMO |
Samsung |
R4-2205017 |
Discussion on RRM requirements for inter-cell beam management |
ZTE Corporation |
R4-2205040 |
Discussion on requirements of inter-cell beam management |
Nokia, Nokia Shanghai Bell |
R4-2205336 |
Discussion on inter-cell L1-RSRP measurement requirements for R17 NR FeMIMO |
Huawei, HiSilicon |
R4-2205844 |
RRM requirements of inter-cell BM in FeMIMO |
Ericsson |
R4-2206770 |
Email discussion summary for [102-e][227] NR_feMIMO_RRM |
Moderator (CMCC) |
R4-2206937 |
DraftCR on Introduction of L1-RSRP measurements on NSC for Rel-17 FeMIMO |
Samsung |
R4-2206938 |
Draft CR on Inter-cell L1-RSRP measurements |
Apple |
R4-2206939 |
draft CR on L1-RSRP measurement requirements for inter-cell BM in R17 |
vivo |
R4-2206940 |
CR for measurement restriction and scheduling availability for inter cell L1-RSRP measurement in R17 |
MediaTek Inc. |
R4-2207068 |
Email discussion summary for [102-e][227] NR_feMIMO_RRM |
Moderator (CMCC) |
10.19.3.3 |
Others |
|
R4-2203776 |
Discussion on other RRM requirements for FeMIMO |
Apple |
R4-2204343 |
Discussion on other RRM impacts in R17 feMIMO |
vivo |
R4-2204367 |
Discussion on general and RRM requirements impacts in R17 feMIMO |
MediaTek Inc. |
R4-2205041 |
Discussion on other items of Rel-17 feMIMO RRM |
Nokia, Nokia Shanghai Bell |
R4-2205337 |
Discussion on other RRM requirements for R17 NR FeMIMO |
Huawei, HiSilicon |
R4-2205338 |
DraftCR on QCL definition for R17 unified TCI |
Huawei, HiSilicon |
R4-2205845 |
Discussion on FeMIMO other open issues |
Ericsson |
R4-2205846 |
Drfat CR on TRP specific Beam Failure Recovery |
Ericsson |
R4-2206941 |
DraftCR on QCL definition for R17 unified TCI |
Huawei, HiSilicon |
R4-2207115 |
Drfat CR on TRP specific Beam Failure Recovery |
Ericsson |
10.19.4.1 |
General |
|
R4-2207207 |
WF on demodulation requirement for Enhancement on Multi-TRP |
Huawei |
R4-2207208 |
WF on demodulation requirement for Enhancement on HST-SFN deployment |
Intel Corporation |
R4-2207209 |
WF on CSI requirement for Rel-17 FeMIMO |
Samsung |
10.19.4.2 |
Demodulation requirements |
|
R4-2204735 |
Over view on Rel-17 FeMIMO demodulation requirements |
SAMSUNG |
R4-2207177 |
Email discussion summary for [102-e][330] NR_FeMIMO_Demod |
Moderator (Samsung) |
R4-2207450 |
Email discussion summary for [102-e][330] NR_FeMIMO_Demod |
Moderator (Samsung) |
10.19.4.2.1 |
Enhancement on HST-SFN scenario |
|
R4-2203777 |
On demod requirements for HST Enahncements |
Apple |
R4-2204163 |
Views on Rel-17 HST-SFN scheme |
NTT DOCOMO, INC. |
R4-2204268 |
Discussion on demodulation requirements for enhancement to support HST-SFN |
CMCC |
R4-2205428 |
Discussion on enhancement on HST-SFN scenario |
Ericsson |
R4-2205774 |
Discussion on UE FeMIMO demod HST-SFN |
Huawei,HiSilicon |
R4-2205920 |
Discussion on demodulation performance requirements definition for Rel-17 enhancements on HST-SFN |
Intel Corporation |
R4-2206100 |
Views on FeMIMO HST Tests |
Qualcomm CDMA Technologies |
10.19.4.2.2 |
Enhancement on Multi-TRP |
|
R4-2203778 |
On demod requirements for multi-TRP Enahncements |
Apple |
R4-2205427 |
Discussion on enhancement on Multi-TRP |
Ericsson |
R4-2205775 |
Discussion on UE FeMIMO demod mTRP |
Huawei,HiSilicon |
R4-2205919 |
Discussion on demodulation performance requirements definition for Rel-17 enhancements on Multi-TRP Tx |
Intel Corporation |
10.19.4.3 |
CSI requirements |
|
R4-2203779 |
On requirements for CSI Enahncements for FeMIMO |
Apple |
R4-2204784 |
Views on FeMIMO CSI requirements |
SAMSUNG |
10.19.4.3.1 |
CSI reporting for Multi-TRP transmission |
|
R4-2205429 |
Discussion on CSI reporting for Multi-TRP transmission |
Ericsson |
R4-2205438 |
On CSI reporting for Multi-TRP transmission for FeMIMO |
Nokia, Nokia Shanghai Bell |
R4-2205776 |
Discussion on UE FeMIMO CSI mTRP |
Huawei,HiSilicon |
R4-2206108 |
Views on FeMIMO CSI Tests |
Qualcomm CDMA Technologies |
10.19.4.3.2 |
Rel-17 eType II port selection codebook |
|
R4-2204829 |
On Rel-17 eType II port selection codebook for FeMIMO |
Nokia, Nokia Shanghai Bell |
R4-2205426 |
Discussion on Rel-17 eType II port selection codebook |
Ericsson |
R4-2205777 |
Discussion on UE FeMIMO CSI FeTypeII PS codebook |
Huawei,HiSilicon |
10.19.4.3.3 |
Others |
|
R4-2205425 |
Discussion on false PMI reporting in inter-cell interference scenario |
Ericsson |
R4-2205778 |
Discussion on UE FeMIMO CSI others |
Huawei,HiSilicon |
R4-2205908 |
Discussion on PMI requirements for inter-cell interference scenario |
MediaTek inc. |
10.20.1 |
General |
|
R4-2206137 |
RedCap draft CR to 38.101-1 |
MediaTek (Chengdu) Inc. |
R4-2206338 |
Email discussion summary for [102-e][138] NR_RedCap |
Moderator (Ericsson) |
R4-2206438 |
Email discussion summary for [102-e][138] NR_RedCap |
Moderator (Ericsson) |
R4-2206544 |
WF on RedCap in Rel-17 |
Ercicson |
R4-2206545 |
LS on FR2 RedCap UE |
Ericsson |
R4-2206634 |
Big CR on RedCap UE FR1-RX |
Ericcon |
R4-2206635 |
Big CR on RedCap UE FR2 |
Big CR on RedCap UE FR2 |
R4-2206642 |
Big CR on RedCap UE FR1-RX |
Ericsson |
10.20.2.1 |
FR1 |
|
R4-2204211 |
RedCap operating bands CR Cat F rel 17 |
Qualcomm Incorporated |
R4-2205278 |
CR for 38.101-1 to introduce RF requirements for RedCap UE |
Huawei, HiSilicon, Deutsche Telekom, CMCC, CBN, Vivo |
R4-2205601 |
RedCap operating bands CR Cat B rel 17 |
Qualcomm Incorporated |
R4-2206135 |
RedCap Tx-Rx separation for FDD |
MediaTek (Chengdu) Inc. |
R4-2206546 |
CR for 38.101-1 to introduce RF requirements for RedCap UE |
Huawei, HiSilicon, Deutsche Telekom, CMCC, CBN, Vivo |
R4-2206550 |
RedCap operating bands CR Cat B rel 17 |
Qualcomm Incorporated |
R4-2206591 |
CR for 38.101-1 to introduce RF requirements for RedCap UE |
Huawei, HiSilicon, Deutsche Telekom, CMCC, CBN, Vivo |
10.20.2.1.1 |
Tx requirements (power class) |
|
R4-2204765 |
On RedCap FR1 Operating band |
ZTE Corporation |
R4-2205275 |
Discussion on FR1 Tx-Rx distance for RedCap UE |
Huawei, HiSilicon |
R4-2205539 |
CR on RedCap UE FR1-TX |
Ericsson |
R4-2205544 |
Remaining issue for RedCap RF requirements in FR1 |
Ericsson |
R4-2206072 |
PC2 HD-FDD for RedCap |
Skyworks Solutions Inc. |
10.20.2.1.2 |
Rx requirements (REFSENS, etc) |
|
R4-2203692 |
RedCap UE REFSENS requirements |
Apple |
R4-2203865 |
RedCap UE HD-FDD REFSENS requirements |
Mediatek India Technology Pvt. |
R4-2204766 |
On RedCap FR1 REFSEN requirements |
ZTE Corporation |
R4-2205276 |
Discussion on FR1 REFSENS requirements for RedCap UE |
Huawei, HiSilicon |
R4-2205540 |
CR on RedCap UE FR1-RX |
Ericsson |
R4-2206547 |
CR on RedCap UE FR1-RX |
Ericsson |
10.20.2.2 |
FR2 |
|
R4-2205277 |
Discussion on FR2 RF requirements for RedCap UE |
Huawei, HiSilicon |
R4-2205279 |
CR for 38.101-2 to introduce RF requirements for FR2 RedCap UE |
Huawei, HiSilicon |
10.20.2.2.1 |
Tx requirements (power class, UE type) |
|
R4-2204040 |
Peak EIRP and EIRP spherical coverage for RedCap FR2 |
Sony |
R4-2204226 |
Further discussion on FR2 RedCap |
MediaTek Beijing Inc. |
R4-2204767 |
Discussion on FR2 RedCap UE |
ZTE Corporation |
R4-2204961 |
Further Discussion on FR2 RedCap Tx requirements |
vivo |
R4-2205119 |
Discussion on RF requirements for FR2 wearable use case Redcap UE |
Xiaomi |
R4-2205541 |
CR on RedCap UE FR2-TX |
Ericsson |
R4-2205545 |
On FR2 RedCap RF requirements |
Ericsson |
R4-2206058 |
On RF requirements for the low-power Redcap FR2 UE |
Qualcomm Incorporated |
R4-2206548 |
CR on RedCap UE FR2-TX |
Ericsson |
10.20.2.2.2 |
Rx requirements |
|
R4-2204041 |
REFSENS and EIS spherical coverage for RedCap FR2 |
Sony |
R4-2204962 |
Further Discussion on FR2 RedCap Rx requirements |
vivo |
R4-2205542 |
CR on RedCap UE FR2-RX |
Ericsson |
R4-2206549 |
CR on RedCap UE FR2-RX |
Ericsson |
10.20.2.3 |
Others |
|
R4-2205543 |
LS on FR2 RedCap UE |
Ericsson |
10.20.3 |
RRM core requirements |
|
R4-2206961 |
Clarification on transmit timing before Msg1 or MsgA retransmission |
Huawei, HiSilicon |
R4-2206971 |
draftCR on inter-RAT NR measurement for RedCap |
Ericsson |
10.20.3.1 |
Impacts from UE complexity reduction |
|
R4-2204798 |
Draft CR for maximum interruption in paging reception for Redcap |
vivo |
R4-2204799 |
Draft CR for Link Recovery Procedures for Redcap |
vivo |
R4-2204800 |
Draft CR for Definitions, symbols and abbreviations for Redcap |
vivo |
R4-2206771 |
Email discussion summary for [102-e][228] NR_redcap_RRM_1 |
Moderator (Ericsson) |
R4-2206888 |
Draft CR for Measurement requirements for Pre-MG in TS 38.133 |
Ericsson |
R4-2206950 |
WF on RedCap RRM requirements |
Ericsson |
R4-2206958 |
Draft CR for maximum interruption in paging reception for Redcap |
vivo |
R4-2206959 |
Draft CR for Definitions, symbols and abbreviations for Redcap |
vivo |
R4-2206964 |
Draft CR for Link Recovery Procedures for Redcap |
vivo |
R4-2207069 |
Email discussion summary for [102-e][228] NR_redcap_RRM_1 |
Moderator (Ericsson) |
10.20.3.1.1 |
General |
|
R4-2203590 |
reply LS on capability related assumptions for RedCap |
ZTE Corporation |
R4-2203591 |
Discussions on general RRM aspects for RedCap UEs |
ZTE Corporation |
R4-2204249 |
Further discussion on general requirements for Redcap UE |
Xiaomi |
R4-2204281 |
Discussion on general requirements on Redcap UE |
OPPO |
R4-2204282 |
draft CR on measurements requirements for inactivate state Redcap UE |
OPPO |
R4-2204321 |
On remaining issues for general aspects on complexity reduction of Redcap |
vivo |
R4-2204902 |
Discussion on general RRM requirements impacts for RedCap UE |
Huawei, Hisilicon |
R4-2204992 |
On general requirements for RedCap UE |
CMCC |
R4-2205512 |
Big CR for RedCap for TS 36.133 |
Ericsson |
R4-2205622 |
Draft CR on RRC_IDLE mode requirements for RedCap for TS 36.133 |
Ericsson |
R4-2205624 |
Big CR for RedCap for TS 38.133 |
Ericsson |
R4-2205625 |
Draft CR on RRC_IDLE mode requirements for RedCap for TS 38.133 |
Ericsson |
R4-2205627 |
Updated worksplit for RedCap for RRM |
Ericsson |
R4-2205628 |
Discussions on general requirements for RedCap |
Ericsson |
R4-2206078 |
Discussion on UE capability, scheduling availability and SDT |
MediaTek inc. |
R4-2206891 |
Draft CR on mgta for NCSG |
Intel |
R4-2206951 |
LS on configuring margin for 1 Rx RedCap Ues |
Ericsson |
R4-2206952 |
LS on NCD-SSB issues for RedCap UE |
Ericsson |
R4-2206953 |
draft CR on measurements requirements for inactivate state Redcap UE |
OPPO |
R4-2206954 |
Draft CR on RRC_IDLE mode requirements for RedCap for TS 36.133 |
Ericsson |
R4-2206955 |
Draft CR on RRC_IDLE mode requirements for RedCap for TS 38.133 |
Ericsson |
R4-2207104 |
LS on NCD-SSB issues for RedCap UE |
Ericsson |
10.20.3.1.2 |
Mobility requirements |
|
R4-2203584 |
Requirements under RRC Connected mode for RedCap UEs |
ZTE Corporation |
R4-2203787 |
Discussion on mobility requirement for RedCap |
Apple |
R4-2204322 |
On remaining issues for mobility requirements for Redcap |
vivo |
R4-2204539 |
Discussion on mobiliy requiremetns for RedCap UEs |
Nokia, Nokia Shanghai Bell |
R4-2204903 |
Discussion on UE mobility requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2204904 |
Draft CR on mobility requirements for Redcap UE |
Huawei, Hisilicon |
R4-2204905 |
Draft CR on E-UTRAN - NR Handover for Redcap UE |
Huawei, Hisilicon |
R4-2204993 |
On mobility requirements for RedCap UE |
CMCC |
R4-2205409 |
Requirements under RRC Connected mode for RedCap UEs |
ZTE Corporation |
R4-2205626 |
Draft CR on RRC_INACTIVE mode requirements for RedCap for TS 38.133 |
Ericsson |
R4-2205629 |
Discussions on RedCap mobility requirements |
Ericsson |
R4-2206038 |
RRC connection release with redireciton for redcap in TS 36.133 |
Ericsson |
R4-2206079 |
Discussion on mobility requirements |
MediaTek inc. |
R4-2206111 |
Mobility requirements for RedCap UEs |
Qualcomm Incorporated |
R4-2206956 |
Draft CR on RRC_INACTIVE mode requirements for RedCap for TS 38.133 |
Ericsson |
R4-2206965 |
Draft CR on mobility requirements for Redcap UE |
Huawei, Hisilicon |
R4-2206966 |
Draft CR on E-UTRAN – NR Handover for Redcap UE |
Huawei, Hisilicon |
R4-2206967 |
RRC connection release with redireciton for redcap in TS 36.133 |
Ericsson |
R4-2207033 |
Draft CR on New gap pattern for MUSIM |
Ericsson, Intel |
10.20.3.1.3 |
Timing requirements |
|
R4-2203585 |
Timing requirements for RedCap UEs |
ZTE Corporation |
R4-2204250 |
Further discussion on timing requirements for Redcap UE |
Xiaomi |
R4-2204906 |
Discussion on UE timing requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2204994 |
On timings requirements for RedCap UE |
CMCC |
R4-2206037 |
Further analysis of UE transmit timing requirements in RedCap |
Ericsson |
R4-2206080 |
UE complexity reduction impact on timing requirements |
MediaTek inc. |
10.20.3.1.4 |
Signalling characteristics |
|
R4-2203586 |
On Signalling characteristics of RedCap UEs |
ZTE Corporation |
R4-2203788 |
Discussion on signalling characteristics for RedCap |
Apple |
R4-2204251 |
Further discussion on signalling characteristics for Redcap UE |
Xiaomi |
R4-2204283 |
Discussion on measurement requirements for RedCap UE |
OPPO |
R4-2204323 |
On remaining issues for signalling characteristics for Redcap |
vivo |
R4-2204536 |
Discussion on signalling characteristics for RedCap UEs |
Nokia, Nokia Shanghai Bell |
R4-2204907 |
Discussion on signaling characteristics due to UE complexity reduction |
Huawei, Hisilicon |
R4-2204995 |
On Signalling characteristics requirements for RedCap UE |
CMCC |
R4-2204996 |
Draft CR to 38.133 for introducing RedCap requirements on active BWP switch delay, active TCI state switching delay and UE specific CBW change |
CMCC |
R4-2205630 |
Discussions on RedCap signaling characteristics |
Ericsson |
R4-2206081 |
Discussion on signaling characteristic in RedCap |
MediaTek inc. |
R4-2206085 |
DraftCR on reduced capability Ues for RLM for RedCap |
MediaTek Inc. |
R4-2206112 |
On Fast BWP switching for RedCap UEs |
Qualcomm Incorporated |
R4-2206962 |
Draft CR to 38.133 for introducing RedCap requirements on active BWP switch delay, active TCI state switching delay and UE specific CBW change |
CMCC |
R4-2206963 |
DraftCR on reduced capability Ues for RLM for RedCap |
MediaTek Inc. |
10.20.3.1.5 |
Measurement procedure |
|
R4-2203587 |
Measurement procedure of RedCap UEs |
ZTE Corporation |
R4-2203789 |
Discussion on cell identification and measurement for RedCap |
Apple |
R4-2204252 |
Further discussion on measurement procedure for Redcap UE |
Xiaomi |
R4-2204284 |
Discussion on signaling characteristics requirements for RedCap UE |
OPPO |
R4-2204324 |
On remaining issues for measurement procedure for Redcap |
vivo |
R4-2204537 |
Draft CR - Introducing L1-RSRP requirements for RedCap UEs |
Nokia, Nokia Shanghai Bell |
R4-2204538 |
Discussion on measurement procedures for RedCap UEs |
Nokia, Nokia Shanghai Bell |
R4-2204908 |
Discussion on measurement requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2204997 |
On Measurement procedure for RedCap UE |
CMCC |
R4-2205511 |
draftCR on inter-RAT NR measurement for RedCap |
Ericsson |
R4-2205631 |
Discussions on RedCap measurement procedure |
Ericsson |
R4-2205938 |
Introduction of RedCap UE in clause 9.11A |
Nokia, Nokia Shanghai Bell |
R4-2206082 |
Measurement procedure for RedCap |
MediaTek inc. |
R4-2206087 |
DraftCR on reduced capability Ues for general measurements and intra-frequency |
MediaTek Inc. |
R4-2206088 |
DraftCR on reduced capability Ues for inter-frequency and inter-RAT measurements |
MediaTek Inc. |
R4-2206113 |
Measurement procedures for 1Rx UEs |
Qualcomm Incorporated |
R4-2206968 |
DraftCR on reduced capability Ues for general measurements and intra-frequency |
MediaTek Inc. |
R4-2206969 |
DraftCR on reduced capability Ues for inter-frequency and inter-RAT measurements |
MediaTek Inc. |
R4-2206970 |
Draft CR – Introducing L1-RSRP requirements for RedCap UEs |
Nokia, Nokia Shanghai Bell |
R4-2206972 |
Introduction of RedCap UE in clause 9.11A |
Nokia, Nokia Shanghai Bell |
10.20.3.2 |
Extended DRX enhancements |
|
R4-2203588 |
On extended DRX enhancements for RedCap |
ZTE Corporation |
R4-2203790 |
Discussion on RRM requirement with eDRX for RedCap |
Apple |
R4-2204246 |
Further discussion on RRM requirements for extended DRX enhancements for RedCap |
Xiaomi |
R4-2204285 |
Discussion on eDRX requirements for RedCap UE |
OPPO |
R4-2204325 |
On remaining issues for Redcap eDRX |
vivo |
R4-2204540 |
Discussion on eDRX enhancements for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2204909 |
Discussion on Extended DRX enhancements for RedCap UE |
Huawei, Hisilicon |
R4-2204910 |
Draft CR on measurement requirements for Redcap UE in inactive mode |
Huawei, Hisilicon |
R4-2204998 |
On Extended DRX cycle for RedCap UE |
CMCC |
R4-2205510 |
Discussions on eDRX requirements for RedCap |
Ericsson |
R4-2206083 |
Extended DRX in IDLE mode and INACTIVE mode |
MediaTek inc. |
R4-2206772 |
Email discussion summary for [102-e][229] NR_redcap_RRM_2 |
Moderator (Vivo) |
R4-2206974 |
WF on eDRX and RRM measurement relaxations requirements for Redcap UE |
Vivo |
R4-2206975 |
Reply LS on RSRP measurement before Msg1 or MsgA retransmission |
Vivo |
R4-2206976 |
LS on RRM relaxation for Redcap |
Vivo |
R4-2206977 |
Reply LS on UE capabilities for RedCap from RRM perspective |
Ericsson |
R4-2206978 |
Draft CR on measurement requirements for Redcap UE in inactive mode |
Huawei, Hisilicon |
R4-2207070 |
Email discussion summary for [102-e][229] NR_redcap_RRM_2 |
Moderator (Vivo) |
R4-2207105 |
WF on eDRX and RRM measurement relaxations requirements for Redcap UE |
Vivo |
R4-2207109 |
LS on RRM relaxation for Redcap |
Vivo |
10.20.3.3 |
RRM measurement relaxations |
|
R4-2203589 |
Discussions on RRM measurement relaxations for RedCap UEs |
ZTE Corporation |
R4-2203791 |
Discussion on RRM relaxation requirement for RedCap |
Apple |
R4-2204247 |
Further discussion on RRM measurement relaxations for RedCap UE |
Xiaomi |
R4-2204286 |
RRM measurement relaxations for RedCap UE |
OPPO |
R4-2204326 |
On remaining issues for Redcap RRM relaxation |
vivo |
R4-2204911 |
Discussion on RRM measurement relaxations for RedCap UE |
Huawei, Hisilicon |
R4-2204999 |
On RRM measurement relaxation for RedCap UE |
CMCC |
R4-2205632 |
Discussions on RRM measurement relaxations |
Ericsson |
R4-2205939 |
On RRM measurement relaxation for neighbouring cells |
Nokia, Nokia Shanghai Bell |
R4-2206084 |
RRM measurements relaxation for stationary criterion |
MediaTek inc. |
10.20.3.4 |
Others |
|
R4-2203792 |
On capability and NCD-SSB design for RedCap RRM |
Apple |
R4-2203891 |
Discussion on other issues to the use of NCD-SSB in RedCap devices |
CATT |
R4-2204248 |
Draft CR on timing requirements for RedCap UE |
Xiaomi |
R4-2204327 |
Further considerations on NCD-SSB for RedCap UE |
vivo |
R4-2204328 |
Reply LS on RSRP measurement before Msg1 or MsgA retransmission |
vivo |
R4-2204912 |
Discussion on RSRP measurement before Msg1 or MsgA retransmission |
Huawei, Hisilicon |
R4-2204913 |
Clarification on transmit timing before Msg1 or MsgA retransmission |
Huawei, Hisilicon |
R4-2205000 |
On NCD-SSB measurement and RedCap capabilitiles |
CMCC |
R4-2205623 |
Draft CR on RRC_INACTIVE mode requirements for RedCap for TS 36.133 |
Ericsson |
R4-2205633 |
RRM Discussions on RedCap UE capabilities |
Ericsson |
R4-2206114 |
NCD-SSB properties and usage for RedCap |
Qualcomm Incorporated |
R4-2206942 |
Draft CR on TRP specific BFR and BFR with two CORESET |
Ericsson |
R4-2206957 |
Draft CR on RRC_INACTIVE mode requirements for RedCap for TS 36.133 |
Ericsson |
R4-2206960 |
Draft CR on timing requirements for RedCap UE |
Xiaomi |
10.20.4 |
UE demodulation and CSI requirements |
|
R4-2205001 |
On UE demodulation and CSI requirements for RedCap UE |
CMCC |
R4-2207178 |
Email discussion summary for [102-e][331] NR_RedCap_Demod |
Moderator (Ericsson) |
R4-2207451 |
Email discussion summary for [102-e][331] NR_RedCap_Demod |
Moderator (Ericsson) |
10.20.4.1 |
General |
|
R4-2205094 |
General issues on UE demodulation and CSI requirements for RedCap |
Ericsson |
R4-2205600 |
Motivation on the support of CRS-IM for Redcap UE |
ZTE Corporation |
R4-2206074 |
Introduction of RedCap Demodulation Requirements |
Qualcomm Incorporated |
R4-2207206 |
WF on RedCap UE demodulation and CQI reporting requirements |
Ericsson |
10.20.4.2 |
Demodulation requirements |
|
R4-2205819 |
Discussion on Demodulation requirements for reduced capability NR devices |
Intel Corporation |
10.20.4.2.1 |
PDSCH/SDR requirements |
|
R4-2203780 |
On PDSCH Demod Requirements for Reduced Capability Devices in NR |
Apple |
R4-2204585 |
Discussion on PDSCH/SDR requirements |
Nokia, Nokia Shanghai Bell |
R4-2205095 |
PDSCH demodulation requirements for RedCap |
Ericsson |
R4-2205804 |
Discussions on common parameters and PDSCH requirements for Rel-17 Redcap UE |
Huawei,HiSilicon |
R4-2205907 |
Discussion for the PDSCH requirements for RedCap |
MediaTek inc. |
10.20.4.2.2 |
PDCCH/PBCH requirements |
|
R4-2203781 |
On PDCCH PBCH Demod Requirements for Reduced Capability Devices in NR |
Apple |
R4-2204586 |
Discussion on PDCCH/PBCH requirements |
Nokia, Nokia Shanghai Bell |
R4-2205096 |
PDCCH/PBCH demodulation requirements for RedCap |
Ericsson |
R4-2205805 |
Discussions on Rel-17 redcap UE PDCCH and PBCH requirements |
Huawei,HiSilicon |
10.20.4.3 |
CSI requirements |
|
R4-2203782 |
On CSI Reporting Requirements for Reduced Capability Devices in NR |
Apple |
R4-2205806 |
Discussions on Rel-17 redcap UE CSI requirements |
Huawei,HiSilicon |
R4-2205820 |
Discussion on CSI requirements for reduced capability NR devices |
Intel Corporation |
10.20.4.3.1 |
CQI requirements |
|
R4-2204587 |
Discussion on CQI requirements |
Nokia, Nokia Shanghai Bell |
R4-2205097 |
CQI reporting requirements for RedCap |
Ericsson |
10.20.4.3.2 |
PMI/RI requirements |
|
R4-2204588 |
Discussion on PMI/RI requirements |
Nokia, Nokia Shanghai Bell |
R4-2205098 |
PMI/RI reporting requirements for RedCap |
Ericsson |
10.21 |
Positioning enhancements for NR |
|
R4-2206989 |
Draft CR to 38.133 Introduction of RSTD measurement requirements for latency reduction |
vivo |
R4-2207088 |
Reply LS on latency improvement for PRS measurement with MG |
Huawei |
R4-2207098 |
On applicable number of PFL for the gapless PRS measurement |
Ericsson |
10.21.1 |
General |
|
R4-2206025 |
Updated work split on RRM core requirements for postioning |
Ericsson |
R4-2206026 |
Big DraftCR on Positioning Enhancement |
Ericsson |
R4-2206643 |
Big CR on RedCap UE FR2 |
Ericsson, Qualcomm |
R4-2206773 |
Email discussion summary for [102-e][230] NR_pos_enh_1 |
Moderator (Ericsson) |
R4-2206973 |
Updated worksplit for RedCap for RRM |
Ericsson |
R4-2206979 |
WF on NR Positioning Enhancements (Part 1) |
Ericsson |
R4-2206980 |
LS on lower Rx beam sweeping factor for latency improvement |
Intel |
R4-2206981 |
LS reply on condition of PRS measurement outside MG |
Vivo |
R4-2206982 |
LS on PRS measurement reporting enhancement |
Nokia |
R4-2206983 |
Updated work split on RRM core requirements for postioning |
Ericsson |
R4-2207071 |
Email discussion summary for [102-e][230] NR_pos_enh_1 |
Moderator (Ericsson) |
R4-2207124 |
Big CR: RRM requirements for Rel-17 NR Positioning Enhancements |
Ericsson |
10.21.2.1 |
UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
|
R4-2203883 |
Discussion on UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
CATT |
R4-2204300 |
Discussion on UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
OPPO |
R4-2204408 |
Discussion on timing mitigating for NR positioning enhancements |
Intel Corporation |
R4-2204463 |
On UE Rx/Tx timing error mitigation |
Qualcomm Incorporated |
R4-2204642 |
Further discussion on timing delay error mitigation |
vivo |
R4-2205379 |
Discussion on timing error mitigation for positioning |
Huawei, HiSilicon |
R4-2205380 |
CR on measurement period requirements with multiple Rx TEGs |
Huawei, HiSilicon |
R4-2205396 |
UE RxTx and gNB RxTx timing delay mitigation |
ZTE Corporation |
R4-2205602 |
On Rx/Tx timing delay mitigation |
Ericsson |
R4-2205940 |
Discussion on timing error mitigation for NR positioning |
Nokia, Nokia Shanghai Bell |
R4-2206774 |
Email discussion summary for [102-e][231] NR_pos_enh_2 |
Moderator (CATT) |
R4-2206997 |
WF on NR Positioning Enhancements (Part 2) |
CATT |
R4-2206998 |
LS on the UE/TRP TEG framework |
CATT |
R4-2206999 |
LS on the UE behavior under cell selection during PRS measurement period |
Ericsson |
R4-2207003 |
CR on measurement period requirements with multiple Rx TEGs |
Huawei, HiSilicon |
R4-2207072 |
Email discussion summary for [102-e][231] NR_pos_enh_2 |
Moderator (CATT) |
10.21.2.2 |
Latency reduction of positioning measurement |
|
R4-2203884 |
Discussion on latency reduction of positioning measurement |
CATT |
R4-2203885 |
Draft CR on PRS-RSRP measurement period without gaps |
CATT |
R4-2203886 |
Draft CR on PRS-RSRPP measurement period without gaps |
CATT |
R4-2204262 |
Discussion on latency reduction of positioning measurement |
CMCC |
R4-2204301 |
Discussion on latency reduction of positioning measurements |
OPPO |
R4-2204302 |
Draft CR to measurement period for UE Rx-Tx time difference measurement without gap |
OPPO |
R4-2204303 |
Draft CR to scheduling availability of UE during RSTD measurement without gap |
OPPO |
R4-2204409 |
Discussion on latency reduction for NR positioning enhancements |
Intel Corporation |
R4-2204412 |
DraftCR to TS 38.133: NR ePos PRS-RSRP with reduced number of samples (9.9.3.5) |
Intel Corporation |
R4-2204464 |
On latency reduction of NR positioning measurements |
Qualcomm Incorporated |
R4-2204638 |
Draft CR to 38.133 Introduction of RSTD measurement requirements for latency reduction |
vivo |
R4-2204639 |
Draft CR to 38.133 Introduction of scheduling availability of UE during UE Rx-Tx time difference measurement without gaps |
vivo |
R4-2204640 |
Further discussion on latency reduction of positioning measurement |
vivo |
R4-2205038 |
Discussion on latency reduction of positioning measurement |
Nokia, Nokia Shanghai Bell |
R4-2205381 |
On latency reduction for positioning measurement |
Huawei, HiSilicon |
R4-2205382 |
CR on requirements for UE Rx-Tx measurement with reduced latency |
Huawei, HiSilicon |
R4-2205397 |
Discussions on latency reduction of positioning measurement |
ZTE Corporation |
R4-2205603 |
On latency reduction of positioning measurement |
Ericsson |
R4-2205605 |
PRS-RSRPP measurement requirements including latency reduction |
Ericsson |
R4-2206984 |
Draft CR on PRS-RSRP measurement period without gaps |
CATT |
R4-2206985 |
Draft CR on PRS-RSRPP measurement period without gaps |
CATT |
R4-2206986 |
Draft CR to measurement period for UE Rx-Tx time difference measurement without gap |
OPPO |
R4-2206987 |
Draft CR to scheduling availability of UE during RSTD measurement without gap |
OPPO |
R4-2206988 |
DraftCR to TS 38.133: NR ePos PRS-RSRP with reduced number of samples (9.9.3.5) |
Intel Corporation |
R4-2206990 |
Draft CR to 38.133 Introduction of scheduling availability of UE during UE Rx-Tx time difference measurement without gaps |
vivo |
R4-2206991 |
CR on requirements for UE Rx-Tx measurement with reduced latency |
Huawei, HiSilicon |
R4-2206992 |
PRS-RSRPP measurement requirements including latency reduction |
Ericsson |
10.21.2.3 |
Measurement in RRC_INACTIVE state |
|
R4-2203887 |
Discussion on measurement in RRC_INACTIVE state |
CATT |
R4-2203888 |
Draft CR on PRS-RSRPP measurement requirements in RRC_INACTIVE state |
CATT |
R4-2204261 |
Discussion on positioning measurement in RRC_INACTIVE state |
CMCC |
R4-2204304 |
Discussion on PRS measurements in RRC_INACTIVE state |
OPPO |
R4-2204410 |
Discussion on measurements in RRC_INACTIVE for NR positioning enhancements |
Intel Corporation |
R4-2204465 |
On NR positioning measurements in RRC_INACTIVE |
Qualcomm Incorporated |
R4-2204466 |
DraftCR - RSTD measurement requirements in RRC_INACTIVE |
Qualcomm Incorporated |
R4-2204637 |
Draft CR to 38.133 Introduction of PRS RSRP measurement requirements in RRC_INACTIVE state |
vivo |
R4-2204641 |
Further discussion on PRS based measurement in RRC_INACTIVE state |
vivo |
R4-2205383 |
Discussion on PRS measurement in RRC_INACTIVE |
Huawei, HiSilicon |
R4-2205384 |
CR on general requirements for PRS measurements in RRC Inactive |
Huawei, HiSilicon |
R4-2205398 |
Positioning measurements in RRC_INACTIVE state |
ZTE Corporation |
R4-2205941 |
Discussion on measurement in RRC_INACTIVE state |
Nokia, Nokia Shanghai Bell |
R4-2206027 |
Further analysis PRS measurement requirements in RRC inactive state |
Ericsson |
R4-2206028 |
UE Rx-Tx measurement requirements in RRC inactive state (clause 5.5.4) |
Ericsson |
R4-2207000 |
Draft CR on PRS-RSRPP measurement requirements in RRC_INACTIVE state |
CATT |
R4-2207001 |
DraftCR - RSTD measurement requirements in RRC_INACTIVE |
Qualcomm Incorporated |
R4-2207002 |
Draft CR to 38.133 Introduction of PRS RSRP measurement requirements in RRC_INACTIVE state |
vivo |
R4-2207004 |
CR on general requirements for PRS measurements in RRC Inactive |
Huawei, HiSilicon |
R4-2207005 |
UE Rx-Tx measurement requirements in RRC inactive state (clause 5.5.4) |
Ericsson |
10.21.2.4 |
Impact on existing UE positioning and RRM requirements |
|
R4-2205385 |
Discussion on MG-less PRS measurement |
Huawei, HiSilicon |
R4-2205386 |
CR on RSTD measurement period requirements without gaps |
Huawei, HiSilicon |
R4-2205399 |
Impact on existing UE positioning and RRM requirements |
ZTE Corporation |
R4-2205606 |
General - PRS measurement without gaps |
Ericsson |
R4-2206993 |
CR on RSTD measurement period requirements without gaps |
Huawei, HiSilicon |
R4-2206994 |
General - PRS measurement without gaps |
Ericsson |
R4-2207103 |
CR: General - PRS measurement without gaps |
Ericsson |
10.21.2.6 |
Others |
|
R4-2204305 |
Other issues of positioning enhancements for NR |
OPPO |
R4-2204643 |
Other issues of positioning enhancement |
vivo |
R4-2205387 |
Discussion on other issues for positioning enhancement |
Huawei, HiSilicon |
R4-2205388 |
CR on scheduling restriction for PRS-RSRPP measurement |
Huawei, HiSilicon |
R4-2205400 |
on PRS measurement outside the measurement gap |
ZTE Corporation |
R4-2205604 |
Impact of enhanced positioning on existing RRM |
Ericsson |
R4-2205607 |
Scheduling availability of UE during PRS-RSRP measurement |
Ericsson |
R4-2206995 |
CR on scheduling restriction for PRS-RSRPP measurement |
Huawei, HiSilicon |
R4-2206996 |
Scheduling availability of UE during PRS-RSRP measurement |
Ericsson |
10.22 |
Multi-Radio Dual-Connectivity enhancements |
|
R4-2207006 |
WF on R17 further Multi-RAT Dual-Connectivity enhancements |
Huawei, HiSilicon |
R4-2207017 |
Draft CR: RRM requirements for efficient activation of SCG |
Nokia |
10.22.1 |
General |
|
R4-2204477 |
LS reply on UE behaviour for deactivated SCG and value range for measCycle |
Ericsson |
R4-2206775 |
Email discussion summary for [102-e][232] LTE_NR_DC_enh2 |
Moderator (Huawei) |
R4-2207019 |
LS reply on UE behaviour for deactivated SCG and value range for measCycle |
Ericsson |
R4-2207073 |
Email discussion summary for [102-e][232] LTE_NR_DC_enh2 |
Moderator (Huawei) |
R4-2207125 |
Big CR: RRM requirements for Rel-17 Further Multi-RAT Dual-Connectivity enhancements (TS 38.133) |
Huawei, HiSilicon |
R4-2207126 |
Big CR: RRM requirements for Rel-17 Further Multi-RAT Dual-Connectivity enhancements (TS 36.133) |
Huawei, HiSilicon |
10.22.2.1 |
Efficient activation/de-activation mechanism for SCells |
|
R4-2203744 |
On efficient activation/de-activation mechanism for SCells |
Apple |
R4-2203858 |
Efficient activation and deactivation mechanism for SCells |
Qualcomm Incorporated |
R4-2204206 |
Discussion on efficient activation/de-activation mechanism for SCell |
MediaTek (Shenzhen) Inc. |
R4-2204287 |
Discussion on efficient activation/de-activation mechanism for Scells |
OPPO |
R4-2204476 |
Discussion On efficient (de)activation mechanism for Scells |
Ericsson |
R4-2204896 |
Discussion on efficient activation/de-activation mechanism for Scells |
Huawei, Hisilicon |
R4-2204897 |
Draft CR on A-TRS based fast SCell activation |
Huawei, Hisilicon |
R4-2205646 |
Efficient activation/de-activation mechanism for Scells |
Nokia, Nokia Shanghai Bell |
R4-2207007 |
Draft CR on A-TRS based fast SCell activation |
Huawei, Hisilicon |
10.22.2.2 |
Efficient activation/de-activation mechanism for one SCG |
|
R4-2203745 |
On efficient activation/de-activation mechanism for one SCG |
Apple |
R4-2203746 |
CR on TS38.133 interruptions due to SCG activation/deactivation |
Apple |
R4-2203747 |
CR on TS36.133 for interruptions due to SCG activation/deactivation |
Apple |
R4-2203859 |
Efficient activation and deactivation mechanism for one SCG |
Qualcomm Incorporated |
R4-2204207 |
Discussion on efficient activation/de-activation mechanism for one SCG |
MediaTek (Shenzhen) Inc. |
R4-2204288 |
Discussion on efficient activation/de-activation mechanism for one SCG |
OPPO |
R4-2204289 |
Draft CR to 38133 on SCG Activation and deactivation delay |
OPPO |
R4-2204290 |
Draft CR to 36133 on SCG Activation and deactivation delay |
OPPO |
R4-2204345 |
CR on 38.133 for Te requirement for first transmission of RACH-less SCG activation |
MediaTek (Shenzhen) Inc. |
R4-2204416 |
DraftCR to TS 38.133 for interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2204417 |
DraftCR to TS 36.133 for interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2204475 |
Discussion On efficient (de)activation mechanism for one SCG |
Ericsson |
R4-2204632 |
DraftCR on L3 and RLM/BFD measurement requirements for deactivated SCG |
vivo |
R4-2204633 |
Further discussion on efficient activationde-activation mechanism for one SCG |
vivo |
R4-2204898 |
Discussion on efficient activation/de-activation mechanism for one SCG |
Huawei, Hisilicon |
R4-2204899 |
Draft CR on measurement requirements on deactivated PSCell |
Huawei, Hisilicon |
R4-2205647 |
Efficient activation/de-activation mechanism for one SCG. |
Nokia, Nokia Shanghai Bell |
R4-2205648 |
Draft CR: RRM requirements for efficient activation of SCG |
Nokia, Nokia Shanghai Bell |
R4-2207009 |
CR on TS38.133 interruptions due to SCG activation/deactivation |
Apple |
R4-2207010 |
CR on TS36.133 for interruptions due to SCG activation/deactivation |
Apple |
R4-2207011 |
Draft CR to 38133 on SCG Activation and deactivation delay |
OPPO |
R4-2207016 |
Draft CR on measurement requirements on deactivated PSCell |
Huawei, Hisilicon |
R4-2207110 |
CR on 38.133 for Te requirement for first transmission of RACH-less SCG activation |
MediaTek (Shenzhen) Inc. |
10.22.2.3 |
Conditional PSCell change and addition |
|
R4-2204900 |
Correction on Conditional PSCell Addition Delay |
Huawei, Hisilicon |
R4-2206847 |
CR on L1-SINR measurement in FR1 HST |
Huawei, Hisilicon |
R4-2207008 |
CR on interruption due to A-TRS based fast SCell activation |
Huawei, Hisilicon |
10.22.2.4 |
Others |
|
R4-2204478 |
Draft CR for introduction of new parameter measCyclePSCell |
Ericsson |
R4-2204901 |
CR on interruption due to A-TRS based fast SCell activation |
Huawei, Hisilicon |
R4-2207102 |
CR on interruption due to A-TRS based fast SCell activation |
Huawei, HiSilicon |
10.23 |
Enhanced IIoT and URLLC support |
|
R4-2207020 |
WF on NR_IIOT_URLLC_enh RRM requirements |
Nokia, Nokia Shanghai Bell |
R4-2207021 |
reply LS on propagation delay compensation |
Huawei, HiSilicon |
10.23.1 |
General |
|
R4-2206015 |
UE features for enhanced IIoT and URLLC |
Nokia |
R4-2206776 |
Email discussion summary for [102-e][233] NR_IIOT_URLLC_enh |
Moderator (Nokia) |
R4-2207074 |
Email discussion summary for [102-e][233] NR_IIOT_URLLC_enh |
Moderator (Nokia) |
R4-2207127 |
Big CR: RRM requirements for Rel-17 Enhanced IIoT and URLLC support |
Nokia, Nokia Shanghai Bell |
10.23.2.1 |
Propagation delay compensation enhancements |
|
R4-2203655 |
Discussion of RRM Requirements for Propagation Delay Compensation Enhancements |
Nokia |
R4-2204306 |
Discussion on propagation delay compensation enhancements |
OPPO |
R4-2204472 |
On RTT-based propagation delay compensation |
Qualcomm Incorporated |
R4-2204647 |
Further discussion on propagation delay compensation enhancements |
vivo |
R4-2204648 |
Simulation results for TRS based PDC |
vivo |
R4-2205389 |
On RRM requirements for PDC enhancements |
Huawei, HiSilicon |
R4-2205390 |
CR on requirements for UE Rx-Tx measurement for PDC |
Huawei, HiSilicon |
R4-2205418 |
Propagation Delay Compensation Enhancements for Time Synchronization |
Ericsson |
R4-2205419 |
Simulation results for Propagation Delay Compensation |
Ericsson |
R4-2205815 |
draftCR on requirements for UE Rx-Tx measurement for propagation delay compensation |
Nokia |
R4-2207025 |
draftCR on requirements for UE Rx-Tx measurement for propagation delay compensation |
Nokia, Nokia Shanghai Bell |
10.23.2.2 |
Reference point for Te requirements |
|
R4-2203656 |
Further discussion on the reference point |
Nokia |
R4-2204423 |
draftCR to clarify timing reference point for UE UL timing test cases R15 |
Intel Corporation |
R4-2204424 |
draftCR to clarify timing reference point for UE UL timing test cases R16 |
Intel Corporation |
R4-2204425 |
draftCR to clarify timing reference point for UE UL timing test cases R17 |
Intel Corporation |
R4-2204649 |
Further discussion on reference point for Te requirements |
vivo |
R4-2205391 |
On reference point for Te requirements |
Huawei, HiSilicon |
R4-2206021 |
LS response on UE transmit timing error |
Ericsson |
R4-2207022 |
draftCR to clarify timing reference point for UE UL timing test cases R15 |
Intel Corporation |
R4-2207101 |
Correction to reference point defintion for UE timing in TS 38.133 |
Ericsson, Intel, Huawei, HiSilicon, Qualcomm |
10.24 |
NR Sidelink Relay |
|
R4-2207026 |
WF on RRM requirements for SL relay |
OPPO |
10.24.1 |
General |
|
R4-2204291 |
Big CR: RRM requirements for NR SL Relay |
OPPO |
R4-2206777 |
Email discussion summary for [102-e][234] NR_SL_relay |
Moderator (OPPO) |
R4-2207075 |
Email discussion summary for [102-e][234] NR_SL_relay |
Moderator (OPPO) |
R4-2207082 |
Big CR: RRM requirements for Rel-17 NR SL Relay |
OPPO |
10.24.2 |
RRM core requirements |
|
R4-2203720 |
On NR SL relay RRM Requirement Scope |
Qualcomm, Inc. |
R4-2204292 |
RRM requirements for SL relay (re)selection |
OPPO |
R4-2205339 |
Discussion on RRM remaining issues for NR sidelink relay |
Huawei, HiSilicon |
R4-2205340 |
DraftCR on interruption requirements for NR sidelink relay |
Huawei, HiSilicon |
R4-2207027 |
DraftCR on interruption requirements for NR sidelink relay |
Huawei, HiSilicon |
10.25 |
NR small data transmissions in INACTIVE state |
|
R4-2207028 |
WF on RRM requirements for NR SDT |
ZTE |
R4-2207111 |
WF on RRM requirements for NR SDT |
ZTE |
10.25.1 |
General and work plan |
|
R4-2207128 |
Big CR: RRM requirements for Rel-17 NR SDT in INACTIVE state |
ZTE |
10.25.2 |
RRM core requirements |
|
R4-2203534 |
TA validation window requirements for CG-SDT |
Nokia, Nokia Shanghai Bell |
R4-2203535 |
Draft CR TA validation for Small Data Transmissions |
Nokia, Nokia Shanghai Bell |
R4-2203796 |
On RRM requirement for CG-SDT |
Apple |
R4-2203867 |
RRM requirements and TA validation windows for CG-SDT |
Qualcomm Incorporated |
R4-2205216 |
Draft big CR for SDT RRM requirements |
ZTE Wistron Telecom AB |
R4-2205217 |
On RRM requirements for NR SDT |
ZTE Wistron Telecom AB |
R4-2205392 |
Discussion on remaining issues for SDT RRM |
Huawei, HiSilicon |
R4-2205393 |
CR on SDT RRM requirements |
Huawei, HiSilicon |
R4-2205638 |
Discussions on RRM requirements for Small Data Transmissions |
Ericsson |
R4-2205639 |
Draft CR TA validation for Small Data Transmissions |
Ericsson |
R4-2205923 |
RRM requirements for CG-SDT |
MediaTek Inc. |
R4-2206778 |
Email discussion summary for [102-e][235] NR_SmallData_INACTIVE |
Moderator (ZTE) |
R4-2206784 |
RRM requirements and TA validation windows for CG-SDT |
Qualcomm Incorporated |
R4-2207029 |
Draft CR TA validation for Small Data Transmissions |
Nokia, Nokia Shanghai Bell |
R4-2207030 |
CR on SDT RRM requirements |
Huawei, HiSilicon |
R4-2207076 |
Email discussion summary for [102-e][235] NR_SmallData_INACTIVE |
Moderator (ZTE) |
10.26 |
Support for Multi-SIM devices for LTE/NR |
|
R4-2207031 |
WF on R17 Support for Multi-SIM devices for LTE-NR |
Vivo |
10.26.1 |
General and work plan |
|
R4-2205513 |
LS response on gap handling for MUSIM |
Ericsson |
R4-2206779 |
Email discussion summary for [102-e][236] LTE_NR_MUSIM |
Moderator (Vivo) |
R4-2207032 |
Reply LS on RAN2’s agreement for MUSIM gaps |
Vivo |
R4-2207077 |
Email discussion summary for [102-e][236] LTE_NR_MUSIM |
Moderator (Vivo) |
R4-2207539 |
Big CR: RRM requirements for Rel-17 NR MUSIM |
vivo |
10.26.2 |
RRM core requirements |
|
R4-2203748 |
On R17 MUSIM |
Apple |
R4-2204161 |
Discussion on MUSIM requirements |
ZTE Corporation |
R4-2204307 |
Discussion on RRM core requirements for Multi-SIM devices |
OPPO |
R4-2204318 |
On remaining issues for Rel-17 MUSIM requirements |
vivo |
R4-2204422 |
Removing square brackets for MUSIM gap patterns |
Intel Corporation |
R4-2205394 |
Discussion on remaining issues for MUSIM |
Huawei, HiSilicon |
R4-2205514 |
New gap pattern for MUSIM |
Ericsson |
R4-2205515 |
draftCR on New gap pattern for MUSIM |
Ericsson, Intel |
R4-2206094 |
Second reply LS on gaps for MUSIM |
Qualcomm Incorporated |
11.1 |
Study on enhanced test methods for FR2 in NR |
|
R4-2203706 |
Proposals to conclude the enhanced test methods study item |
Apple |
R4-2207179 |
Email discussion summary for [102-e][337] FR2_enhTestMethods_Part1 |
Moderator (Intel) |
R4-2207201 |
WF on FR2-2 OTA test methods |
Intel Corporation |
R4-2207452 |
Email discussion summary for [102-e][337] FR2_enhTestMethods_Part1 |
Moderator (Intel) |
R4-2207512 |
TR38.884 Study on enhanced test methods for FR2 NR UEs v1.4.0 |
Apple, vivo, Intel |
11.1.2.1 |
General |
|
R4-2206092 |
TP for TR 38.884 on NR test methods extension to FR2-2 |
Intel Corporation |
R4-2206109 |
MIMO EVM Measurement for FR2 |
Lenovo |
R4-2207202 |
TP for TR 38.884 on NR test methods extension to FR2-2 |
Intel Corporation |
11.1.2.1.2 |
UE types |
|
R4-2203636 |
On FR2-2 Antenna Assumptions |
Keysight Technologies UK Ltd |
R4-2205007 |
Discussion on FR2-2 OTA test methods |
Huawei,HiSilicon |
11.1.2.1.4 |
Others |
|
R4-2204964 |
TP to TR38.884 on applicability extension of test methods for band FR2-2 |
vivo |
R4-2206091 |
On general aspects and UE testing methodology for FR2-2 |
Intel Corporation |
11.1.2.2 |
Test methodology for UE RF |
|
R4-2204965 |
Discussion on test methods for FR2-2 |
vivo |
R4-2206116 |
MIMO EVM Measurement for FR2 |
Lenovo |
11.1.2.3 |
Test methodology for RRM |
|
R4-2203704 |
TP to TR38.884 on minimum SNR for RRM test cases for band n263 |
Apple |
R4-2205915 |
FR2-2 OTA test methods for UE RRM |
Intel Corporation |
11.1.2.4 |
Test methodology for UE demodulation and CSI |
|
R4-2203705 |
TP to TR38.884 on minimum SNR for demodulation test cases for band n263 |
Apple |
R4-2204386 |
FR2-2 OTA test methods for UE demodulation |
Intel Corporation |
R4-2207203 |
TP to TR38.884 on minimum SNR for RRM test cases for band n263 |
Apple |
R4-2207204 |
TP to TR38.884 on minimum SNR for demodulation test cases for band n263 |
Apple |
R4-2207459 |
TP to TR38.884 on minimum SNR for demodulation test cases for band n263 |
Apple |
11.2 |
Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
|
R4-2206551 |
WF on BS Tx Requirements |
Ericsson |
11.2.1 |
General and TR |
|
R4-2203668 |
Further corrections to the solution based on overlapping channels from the network perspective |
Apple |
R4-2204413 |
TP to TR 38.844: General Updates |
Intel Corporation |
R4-2205018 |
draft TR 38.844 v0.0.7 |
Ericsson |
R4-2205072 |
TP to TR 38.844: Editorial updates |
Ericsson |
R4-2205821 |
TP to TR 38.844: Summary and Conclusions |
Intel Corporation, Ericsson |
R4-2205867 |
Views on BS TX Channel BW Filters |
Intel Corporation |
R4-2205956 |
TP to TR 38.844: corrections |
Nokia, Nokia Shanghai Bell |
R4-2206339 |
Email discussion summary for [102-e][139] FS_NR_eff_BW_util |
Moderator (Ericsson) |
R4-2206439 |
Email discussion summary for [102-e][139] FS_NR_eff_BW_util |
Moderator (Ericsson) |
R4-2206552 |
draft TR 38.844 v0.0.7 |
Ericsson |
R4-2206553 |
TP to TR 38.844: General updates |
Intel Corporation |
R4-2206554 |
TP to TR 38.844: Editorial clean up |
Nokia, Nokia Shanghai Bell |
R4-2206555 |
TP to TR 38.844: corrections |
Nokia, Nokia Shanghai Bell |
R4-2206559 |
TP to TR 38.844: Summary and Conclusions |
Intel Corporation, Ericsson |
11.2.2 |
Evaluation of use of larger channel bandwidths than licensed bandwidth |
|
R4-2205156 |
TP for wider channel bandwidth |
Huawei, HiSilicon |
11.2.2.1 |
Channel filter assumptions and RB blanking with impacts on UE (ACS, blocking) |
|
R4-2203669 |
Further input on performance when using the next larger channel |
Apple |
R4-2205212 |
TP to TR 38.844 clause 6.1.3 |
Nokia, Nokia Shanghai Bell |
11.2.2.2 |
Signaling and configuration (RAN1/RAN2 impacts) aspects |
|
R4-2204514 |
Considerations for wider CBW solutions |
China Telecom |
R4-2204515 |
Considerations for wider CBW solutions |
China Telecom |
R4-2204516 |
TP to TR 38.844: Clause 6.1.2.x Spec impact identification |
Qualcomm Incorporated |
R4-2204622 |
TP for 38.844: configuration for the case of larger channel bandwidths than licensed bandwidth |
Ericsson |
R4-2205213 |
TP to TR 38.844 on Larger CBW approach: Signalling and configuration aspects |
Nokia, Nokia Shanghai Bell |
R4-2206557 |
TP to TR 38.844 on Larger CBW approach: Signalling and configuration aspects |
Nokia, Nokia Shanghai Bell |
R4-2206595 |
TP to TR 38.844: Clause 6.1.2.x Spec impact identification |
Qualcomm Incorporated |
11.2.2.3 |
Other aspects such as detailed solution, complexity, legacy UE, etc |
|
R4-2205214 |
TP to TR 38.844 on Larger CBW approach: Legacy UE and RAN4 spec impacts |
Nokia, Nokia Shanghai Bell |
11.2.3.3 |
Overlapping CA (two cells) |
|
R4-2205157 |
TP for overlapping CA |
Huawei, HiSilicon |
R4-2205226 |
Revision on Section 6.7.3 for TR 38.844 |
ZTE Wistron Telecom AB |
R4-2206558 |
TP for overlapping CA |
Huawei, HiSilicon |
11.2.3.4 |
Overall method comparisons |
|
R4-2205158 |
TP for overall method comparisons |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
R4-2205215 |
TP to TR 38.844 Overall method comparison |
Nokia, Nokia Shanghai Bell |
R4-2206560 |
TP for overall method comparisons |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
11.3 |
Study on band combination handling in RAN4 |
|
R4-2206561 |
WF on further simplification for band combinations |
ZTE |
11.3.1 |
General and TR |
|
R4-2203987 |
TR 38.862 V060 Band combination handling |
ZTE Corporation |
R4-2204010 |
TP to TR 38.862 on symbols and abbreviations |
ZTE Corporation |
R4-2206340 |
Email discussion summary for [102-e][140] FS_BC_handling |
Moderator (ZTE) |
R4-2206440 |
Email discussion summary for [102-e][140] FS_BC_handling |
Moderator (ZTE) |
11.3.2 |
Information of rules and guidelines of specifying band combinations (TP format, notation, band configurations, BCS) |
|
R4-2204760 |
Update template for Rel-18 NR CA and SUL band combinations |
ZTE Corporation |
R4-2205666 |
TP to TR38.862 on BC not for block approval and guidelines on single band UL configurations using intra-band UL CA |
Skyworks Solutions Inc. |
R4-2205707 |
TP to 38.862 on that higher order TP(s) are pending approval of fallback(s) |
Ericsson |
R4-2205708 |
TP to 38.862 on rule about not merging cells in CA configuration tables |
Ericsson |
R4-2206562 |
TP to TR38.862 on BC not for block approval and guidelines on single band UL configurations using intra-band UL CA |
Skyworks Solutions Inc. |
11.3.3.1 |
Optimization of delta TIB and delta RIB |
|
R4-2204011 |
TP to TR 38.862 on template of delta TIB and RIB tables |
ZTE Corporation |
R4-2204785 |
TP to TR 38.862: Statistics of dTib and dRib |
Nokia, Nokia Shanghai Bell |
11.3.3.2 |
Optimizations for other redundancy |
|
R4-2204005 |
Further discussion on simplification for DC configuration table in Rel-18 |
ZTE Corporation |
R4-2204009 |
TP to TR 38.862 on simplification for EN-DC and NE-DC configuration tables |
ZTE Corporation |
11.4 |
Optimizations of pi/2 BPSK uplink power in NR |
|
R4-2206563 |
WF for optimizations of Pi/2 BPSK uplink power |
Qualcomm, Skyworks |
R4-2206564 |
TP containing contributions to RAN4#102-e |
Qualcomm |
R4-2206574 |
TR for SI on optimizations of pi_2 BPSK uplink power |
Qualcomm |
R4-2206596 |
TR for SI on optimizations of pi_2 BPSK uplink power |
Qualcomm |
R4-2206598 |
WF for optimizations of Pi/2 BPSK uplink power |
Main Session |
R4-2206609 |
TR for SI on optimizations of pi_2 BPSK uplink power |
Qualcomm |
11.4.1 |
General and TR |
|
R4-2204012 |
TR skeleton for SI on optimizations of pi_2 BPSK uplink power |
Qualcomm Incorporated |
R4-2204013 |
TP for Pi/2 BPSK study item for TR38.868 |
Qualcomm Incorporated |
R4-2204414 |
TP for TR 38.868: Filter Analysis Update |
Intel Corporation |
R4-2206341 |
Email discussion summary for [102-e][141] FS_NR_Opt_pi2BPSK |
Moderator (Qualcomm) |
R4-2206441 |
Email discussion summary for [102-e][141] FS_NR_Opt_pi2BPSK |
Moderator (Qualcomm) |
R4-2206606 |
Email discussion summary for [102-e][141] FS_NR_Opt_pi2BPSK |
Moderator (Qualcomm) |
11.4.2 |
UE Tx power and related issues |
|
R4-2203682 |
PI/2 BPSK enhancements |
Apple |
R4-2204085 |
On Remaining Issues for Optimisations of Pi/2 BPSK UL Power |
Huawei, HiSilicon |
R4-2204481 |
Discussion on Pi_2_BPSK power boosting |
MediaTek Inc. |
R4-2204794 |
Transmitter performance for pi/2 BPSK with spectral shaping |
Nokia, Nokia Shanghai Bell |
R4-2204937 |
Further discussion on pi/2 BPSK UE Tx power |
vivo |
R4-2206139 |
MPR Proposal for PC2 Pi_2 BPSK |
Skyworks Solutions Inc. |
11.4.3 |
Evaluation of filter requirements applicable to identified new UE power capability |
|
R4-2204415 |
Views on Tx+Rx link margin filter delta |
Intel Corporation |
R4-2204795 |
Shaping filter characteristics including transmitter and link performance |
Nokia, Nokia Shanghai Bell |
11.4.4 |
Link level simulations |
|
R4-2204796 |
Receiver performance for pi/2 BPSK with spectral shaping |
Nokia, Nokia Shanghai Bell |
11.4.6 |
Identify RAN4 requirements |
|
R4-2204016 |
PC2 power boost for Pi/2 BPSK |
Qualcomm Incorporated |
R4-2204797 |
Identify?potential changes for?RAN4 requirements |
Nokia, Nokia Shanghai Bell |
12.1.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204496 |
Revised WID: Rel17 LTE inter-band CA for 2 bands DL with 1 band UL |
Qualcomm Incorporated |
R4-2204497 |
TR 36.717-02-01 Rel-17 LTE inter-band CA for 2 bands DL and 1 band UL CA |
Qualcomm Incorporated |
R4-2204498 |
Big CR to TS36.101: Rel-17 LTE inter-band CA for 2 bands DL and 1 band UL CA |
Qualcomm Incorporated |
R4-2206322 |
Email discussion summary for [102-e][122] LTE_Baskets |
Moderator (Ericsson) |
12.2.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2206637 |
Revised WID: LTE inter-band Carrier Aggregation for 3 bands DL with 1 band UL |
Huawei |
R4-2206638 |
TR 36.717-03-01 LTE inter-band Carrier Aggregation for 3 bands DL with 1 band UL |
Main Session |
R4-2206639 |
Big CR to TS 36.101: LTE inter-band Carrier Aggregation for 3 bands DL with 1 band UL |
Huawei |
12.3.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205951 |
Revised WID: LTE Advanced inter-band CA Rel-17 for x bands DL (x=4, 5, 6) with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2205952 |
TR 36.717-04-01 v0.8.0 |
Nokia, Nokia Shanghai Bell |
R4-2205953 |
Updated scope of TR: LTE inter-band CA for 4/5/6 bands DL with 1 band UL |
Nokia, Nokia Shanghai Bell |
R4-2206097 |
Big CR to TS36.101: LTE Advanced inter-band CA Rel-17 for x bands DL (x=4, 5, 6) with 1 band UL |
Nokia, Nokia Shanghai Bell |
12.3.2 |
UE RF with 4 LTE bands CA |
|
R4-2205269 |
Draft CR for 36.101 to add the band combination CA_1-3-28-32 |
Huawei, HiSilicon |
12.4 |
LTE inter-band Carrier Aggregation for 2 bands DL with 2 band UL |
|
R4-2206644 |
TR 36.717-02-02 v0.5.0 |
Huawei, HiSilicon |
12.4.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2205594 |
TR 36.717-02-02 v0.4.0 |
Huawei, HiSilicon |
R4-2205595 |
Big CR for TS 36.101: Introduction of completed LTE CA for 2 bands DL with 2 bands UL (Rel-17) |
Huawei, HiSilicon |
R4-2205596 |
Revised WID for LTE inter-band CA for 2 bands DL with 2 bands UL |
Huawei, HiSilicon |
12.5.1 |
Rapporteur Input (WID/TR/CR) |
|
R4-2204473 |
TR 36.717-03-02 v1.0.0 TR update for LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics France |
R4-2204485 |
Revised WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics France |
R4-2204493 |
Introduction of LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL to TS36.101 |
LG Electronics France |
12.8 |
Upper 700MHz A Block new E-UTRA band in US |
|
R4-2204346 |
TR 36.779 Update (v0.1.0) |
Puloli |
R4-2206323 |
Email discussion summary for [102-e][123] LTE_Upper_700MHz |
Moderator (Huawei) |
R4-2206423 |
Email discussion summary for [102-e][123] LTE_Upper_700MHz |
Moderator (Huawei) |
12.8.3 |
UE RF requirements |
|
R4-2204460 |
Introduction of upper 700MHz A block into TS 36.101 |
Puloli |
R4-2204487 |
Introduction of upper 700MHz A block into TS 38.101 |
Puloli |
R4-2206490 |
Introduction of upper 700MHz A block into TS 36.101 |
Puloli |
R4-2206491 |
Introduction of upper 700MHz A block into TS 38.101 |
Puloli |
12.8.4 |
BS RF requirements |
|
R4-2204352 |
CR to TS36.104 on introduction of upper 700MHz A block |
Baicells |
R4-2204353 |
CR to TS37.104 on introduction of upper 700MHz A block |
Baicells |
R4-2204354 |
CR to TS37.105 on introduction of upper 700MHz A block |
Baicells |
R4-2204355 |
CR to TS38.104 on introduction of upper 700MHz A block |
Baicells |
R4-2205989 |
CR to TS 37.145-1: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
R4-2205990 |
CR to TS 37.145-2: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
R4-2205991 |
CR to TS 38.141-1: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
R4-2205992 |
CR to TS 38.141-2: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
R4-2206492 |
CR to TS36.104 on introduction of upper 700MHz A block |
Baicells |
R4-2206493 |
CR to TS37.104 on introduction of upper 700MHz A block |
Baicells |
R4-2206494 |
CR to TS37.105 on introduction of upper 700MHz A block |
Baicells |
R4-2206495 |
CR to TS38.104 on introduction of upper 700MHz A block |
Baicells |
R4-2206496 |
CR to TS 37.145-1: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
R4-2206497 |
CR to TS 37.145-2: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
R4-2206498 |
CR to TS 38.141-1: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
R4-2206499 |
CR to TS 38.141-2: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
12.8.5 |
Others |
|
R4-2204356 |
CR to TS36.141 on introduction of upper 700MHz A block |
Baicells |
R4-2204357 |
CR to TS37.141 on introduction of upper 700MHz A block |
Baicells |
R4-2205993 |
CR to TS 36.133: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
R4-2206500 |
CR to TS36.141 on introduction of upper 700MHz A block |
Baicells |
R4-2206501 |
CR to TS37.141 on introduction of upper 700MHz A block |
Baicells |
R4-2206502 |
CR to TS 36.133: implementation of LTE_upper_700MHz_A band 103 |
Huawei, HiSilicon |
12.9.2.1 |
BS RF requirements |
|
R4-2204077 |
CR to TS16104 Addition of NB-IoT 16QAM |
Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell |
R4-2204078 |
CR to TS16141 Addition of NB-IoT 16QAM |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson |
12.9.3.1 |
UE RF requirements |
|
R4-2204042 |
On max power reduction for PRACH, PUCCH, and full-PRB PUSCH |
Sony |
R4-2205546 |
RF impact analysis on R17 eMTC WID |
Ericsson |
12.9.4 |
RRM core requirements |
|
R4-2207034 |
WF on RRM requirements for Rel-17 NB-IoT and LTE-MTC |
Huawei, Hisilicon |
12.9.4.1 |
Neighbour cell measurement in RRC Connected state for NB-IoT |
|
R4-2204470 |
On NB-IoT neighbor cell measurements in RRC_CONNECTED |
Qualcomm Incorporated |
R4-2204882 |
Discussion on RRM requirements for Rel-17 NB-IoT |
Huawei, Hisilicon |
R4-2204883 |
Draft CR on intra-frequency measuremnet requiremensts for Rel-17 NB-IoT |
Huawei, Hisilicon |
R4-2204884 |
Big CR of RRM requirements for Rel-17 NB-IoT and eMTC |
Huawei, Hisilicon |
R4-2205634 |
Draft CR on Connected mode inter-frequency neighbour cell measurement before RLF for Rel-17 NB-IoT |
Ericsson |
R4-2205635 |
Discussions on remaining issues of RRM requirements for NB-IoT |
Ericsson |
R4-2206780 |
Email discussion summary for [102-e][237] NB_IOTenh4_LTE_eMTC6_RRM |
Moderator (Huawei) |
R4-2207036 |
Draft CR on Connected mode inter-frequency neighbour cell measurement before RLF for Rel-17 NB-IoT |
Ericsson |
R4-2207078 |
Email discussion summary for [102-e][237] NB_IOTenh4_LTE_eMTC6_RRM |
Moderator (Huawei) |
R4-2207083 |
Big CR of RRM requirements for Rel-17 NB-IoT and eMTC |
Huawei, Hisilicon |
12.9.5 |
Others |
|
R4-2205090 |
draft CR: Introduction of channel quality report for NB-IoT supporting 16QAM |
Ericsson |
R4-2207037 |
draft CR: Introduction of channel quality report for NB-IoT supporting 16QAM |
Ericsson |
12.9.6 |
Demodulation requirements |
|
R4-2207180 |
Email discussion summary for [102-e][333] NB-IOT_MTC_Demod |
Moderator (Huawei) |
R4-2207200 |
WF on Rel-17 NB-IOT and eMTC performance requirements |
Huawei |
R4-2207453 |
Email discussion summary for [102-e][333] NB-IOT_MTC_Demod |
Moderator (Huawei) |
12.9.6.2.1 |
UE demodulation requirements |
|
R4-2204469 |
On UE performance requirements for 16-QAM NB-IoT |
Qualcomm Incorporated |
R4-2205091 |
UE demodulation requirements for Rel-17 NB-IoT |
Ericsson |
R4-2205807 |
Discussions on Rel-17 NB-IOT UE requirements |
Huawei,HiSilicon |
12.9.6.2.2 |
BS demodulation requirements |
|
R4-2203549 |
View on demodulation requirement for Rel-17 NB-IoT |
Samsung |
R4-2205092 |
BS demodulation requirements for Rel-17 NB-IoT |
Ericsson |
R4-2205808 |
Discussions on Rel-17 NB-IOT BS requirements |
Huawei,HiSilicon |
R4-2205942 |
Discussion on BS demodulation requirements for Additional enhancements for NB-IoT |
Nokia, Nokia Shanghai Bell |
12.9.6.3 |
Demodulation requirements for MTC |
|
R4-2203548 |
View on demodulation requirement for Rel-17 eMTC |
Samsung |
R4-2205093 |
UE demodulation requirements for Rel-17 LTE-MTC |
Ericsson |
R4-2205809 |
Discussions on Rel-17 eMTC UE requirements |
Huawei,HiSilicon |
13.1.1 |
LS reply for beam correspondence with SDT in RRC_INACTIVE |
|
R4-2205597 |
Reply LS on beam correspondence with SDT in RRC_INACTIVE |
Huawei, HiSilicon |
R4-2206342 |
Email discussion summary for [102-e][142] NR_reply_LS_UE_RF |
Moderator (Apple) |
R4-2206442 |
Email discussion summary for [102-e][142] NR_reply_LS_UE_RF |
Moderator (Apple) |
R4-2206566 |
Reply LS on power control for NR-DC |
OPPO |
R4-2206567 |
Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
Huawe |
R4-2206586 |
Reply LS on beam correspondence with SDT in RRC_INACTIVE |
Huawei, HiSilicon |
13.1.2 |
RAN5 response LS on LTE REFSENS exception simplification (R5-215803) |
|
R4-2205271 |
Response LS to RAN5 on LTE REFSENS Exceptions Simplification |
Huawei, HiSilicon |
R4-2205272 |
CR for 36.101 on LTE REFSENS exception simplification |
Huawei, HiSilicon |
R4-2206569 |
CR for 36.101 on LTE REFSENS exception simplification |
Huawei, HiSilicon |
13.1.3 |
Others |
|
R4-2203554 |
Discussion on devices certified in a subset of a 3GPP band |
TELUS |
R4-2204974 |
Discussion and Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
vivo |
13.2.1 |
FR2 power control for NR-DC |
|
R4-2204973 |
Discussion and Reply LS on Further Reply LS on power control for NR-DC |
vivo |
R4-2204980 |
R17 FR2 power control for NR-DC and draft LS |
OPPO |
R4-2206059 |
On FR2 power control for inter-band NR-DC |
Qualcomm Incorporated |
13.2.2 |
FR2 requirement applicability over ETC |
|
R4-2203702 |
ETC applicability for FR2 requirements |
Apple |
R4-2204816 |
R15 Reply LS on FR2 ETC |
OPPO |
R4-2204963 |
Reply LS on applicability of RF requirements on extreme tempreture condition |
vivo |
R4-2205194 |
Reply LS on FR2 Extreme temperature conditions clarifications |
Huawei, HiSilicon |
R4-2206060 |
On reply to RAN5 on FR2 requirement applicability over ETC |
Qualcomm Incorporated |
R4-2206570 |
Reply LS on applicability of RF requirements on extreme tempreture condition |
vivo |
13.2.3 |
FR2 UE relative power control tolerance requirements |
|
R4-2204623 |
Draft Reply to LS on FR2 UE relative power control tolerance requirements |
Ericsson |
R4-2205192 |
Reply LS on FR2 UE relative power control tolerance requirements |
Huawei, HiSilicon |
R4-2206061 |
On RAN5 request for change to FR2 UE relative power control tolerance requirements |
Qualcomm Incorporated |
13.2.5 |
Ambiguity issue in deciding TL,C |
|
R4-2205270 |
Reply LS on ambiguity in deciding TL,C |
Huawei, HiSilicon |
13.2.6 |
RAN2 LS on RRM relaxation for Rel-16 power saving (R2-2108877) |
|
R4-2203909 |
Discussion on the inconsistency issue of power saving for higher priority frequency layer |
CATT |
R4-2203910 |
Draft reply LS to RAN2 on RRM relaxation in power saving |
CATT |
R4-2204801 |
Draft CR for requirement alignment for UE power saving measurement requirements |
vivo |
R4-2204805 |
Considerations on remaining issue for Rel-16 UE power saving |
vivo |
R4-2204914 |
Reply LS on RRM relaxation in power saving |
Huawei, Hisilicon |
R4-2204915 |
Correction on measurement requirements in relaxed measurement R16 |
Huawei, Hisilicon |
R4-2204916 |
Correction on measurement requirements in relaxed measurement R17 |
Huawei, Hisilicon |
R4-2205207 |
Correction on measurement requirements in relaxed measurement R16 |
Huawei, Hisilicon |
R4-2205208 |
Correction on measurement requirements in relaxed measurement R17 |
Huawei, Hisilicon |
R4-2205436 |
On RAN2 LS on RRM relaxation for Rel-16 power saving |
ZTE Corporation |
R4-2206781 |
Email discussion summary for [102-e][238] LS_reply_L3_filter_R2-2111590 |
Moderator (Apple) |
R4-2207038 |
Reply LS to RAN2 on RRM relaxation in power saving |
CATT |
R4-2207039 |
Correction on measurement requirements in relaxed measurement R16 |
Huawei, Hisilicon |
R4-2207040 |
Correction to Rel-16 UE relaxed measurement requirements |
Ericsson |
R4-2207079 |
Email discussion summary for [102-e][238] LS_reply_L3_filter_R2-2111590 |
Moderator (Apple) |
13.2.7 |
RAN2 LS on L3 filter configuration (R2-2111590) |
|
R4-2204351 |
Discussion on L3 filter configuration |
Apple |
R4-2205395 |
Reply LS on L3 filter configuration |
Huawei, HiSilicon |
R4-2205525 |
LS reply to RAN4 on L3 filter configuration |
Ericsson |
R4-2205653 |
Incoming LS from RAN2 on L3 filter |
Nokia, Nokia Shanghai Bell |
R4-2206782 |
Email discussion summary for [102-e][239] LS_reply_NR_UE_pow_sav_R2-2108877 |
Moderator (CATT) |
R4-2207041 |
Reply LS to RAN2 on L3 filter configuration |
Apple |
R4-2207080 |
Email discussion summary for [102-e][239] LS_reply_NR_UE_pow_sav_R2-2108877 |
Moderator (CATT) |
13.2.8 |
Others |
|
R4-2204624 |
Draft Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
Ericsson |
R4-2204768 |
Discussion on reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
ZTE Corporation |
R4-2204817 |
R15 Reply LS on Pemax in EN-DC |
OPPO |
R4-2205193 |
Discussion and reply draft LS on configuration of p-MaxEUTRA and p-NR-FR1 |
Huawei, HiSilicon |
R4-2206101 |
Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
Qualcomm Incorporated |
R4-2206568 |
LS On Canada band n77 |
Telus, Bell Mobility |
14.2 |
R18 new proposals |
|
R4-2203558 |
Motivation for new WI on air-to-ground network for NR |
CMCC |
R4-2203559 |
New WID on air-to-ground network for NR |
CMCC |
R4-2203560 |
Motivation for new WID on Home Base Station for NR |
CMCC |
R4-2203561 |
New WID on Home Base Station for NR |
CMCC |
R4-2203701 |
Conditional non-simultaneous Rx/Tx operation as a mitigation for high MSD |
Apple |
R4-2203810 |
Rel-18 proposal on FR2 coverage/performance enhancements |
Apple |
R4-2204046 |
New WID for Rel-18 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2204061 |
Draft new WID on further NR and MR-DC measurement gap enhancements |
MediaTek inc. |
R4-2204215 |
Motivation on defining 8Rx performance requirements for NR |
SoftBank Corp. |
R4-2204546 |
Rel-18 new basket WID on high power UE (power class 2) for NR FDD band |
China Unicom |
R4-2204547 |
Rel-18 new WID on High power UE for NR inter-band CA with 2 UL bands for 26dBm on FDD band |
China Unicom |
R4-2204591 |
Intra-band non-collocated EN-DC/NR-CA |
KDDI Corporation, LG Uplus, NTT DOCOMO, INC., SoftBank Corp. |
R4-2204778 |
Motivation on basket WID on 4Rx and 8Rx bands |
ZTE Corporation |
R4-2204779 |
New WID on 4Rx_8Rx support for NR bands |
ZTE,China Telecom |
R4-2204780 |
New WID on Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
R4-2204781 |
New WID on Rel-18 NR Inter-band Carrier AggregationDual Connectivity for 3 bands DL with 2 bands UL |
ZTE Corporation |
R4-2204782 |
New WID on Rel-18 Dual Connectivity (DC) x bands (x=1,2) LTE inter-band CA (xDL/xUL) and y bands (y=3-x) NR inter-band CA |
ZTE Corporation |
R4-2204783 |
New WID on Rel-18 Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL1UL) and 3 bands NR inter-band CA (3DL1UL) |
ZTE Corporation |
R4-2204923 |
Motivation on simplification of band combination specification |
ZTE Corporation |
R4-2204924 |
Draft New SID on simplification of band combination specification |
ZTE Corporation |
R4-2205071 |
Draft Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
R4-2205480 |
Support of ATG for 5G Advanced |
ZTE Corporation |
R4-2205481 |
Motivation on study on NR NTN RF requirement for coexistence with TN standalone NB-IoT |
ZTE Corporation |
R4-2205482 |
New SI proposal: Study on NR NTN RF requirement for coexistence with TN standalone NB-IoT |
ZTE Corporation |
R4-2205483 |
Views on NR UE RF enhancement in Rel-18 |
ZTE Corporation |
R4-2205484 |
Views on NR BS RF enhancement in Rel-18 |
ZTE Corporation |
R4-2205485 |
Views on NR UE RRM enhancement in Rel-18 |
ZTE Corporation |
R4-2205486 |
Motivation on the support of CRS-IM for Redcap UE |
ZTE Corporation |
R4-2205691 |
New WID: Power Class 1.5 for NR CA with xDL and 2UL (1FDD+1TDD); (x= 2, 3, 4) |
Ericsson |
R4-2206039 |
Motivation for BS EMC Test Simplification |
Ericsson |
R4-2206040 |
New WID: BS/UE EMC enhancements |
Ericsson, Xiaomi |
16 |
Close of the E-meeting |
|
R4-2206160 |
(reserved) |
ETSI MCC |
R4-2206161 |
(reserved) |
ETSI MCC |
R4-2206162 |
(reserved) |
ETSI MCC |
R4-2206163 |
(reserved) |
ETSI MCC |
R4-2206164 |
(reserved) |
ETSI MCC |
R4-2206165 |
(reserved) |
ETSI MCC |
R4-2206166 |
(reserved) |
ETSI MCC |
R4-2206167 |
(reserved) |
ETSI MCC |
R4-2206168 |
(reserved) |
ETSI MCC |
R4-2206169 |
(reserved) |
ETSI MCC |
R4-2206170 |
(reserved) |
ETSI MCC |
R4-2206171 |
(reserved) |
ETSI MCC |
R4-2206172 |
(reserved) |
ETSI MCC |
R4-2206173 |
(reserved) |
ETSI MCC |
R4-2206174 |
(reserved) |
ETSI MCC |
R4-2206175 |
(reserved) |
ETSI MCC |
R4-2206176 |
(reserved) |
ETSI MCC |
R4-2206177 |
(reserved) |
ETSI MCC |
R4-2206178 |
(reserved) |
ETSI MCC |
R4-2206179 |
(reserved) |
ETSI MCC |
R4-2206180 |
(reserved) |
ETSI MCC |
R4-2206181 |
(reserved) |
ETSI MCC |
R4-2206182 |
(reserved) |
ETSI MCC |
R4-2206183 |
(reserved) |
ETSI MCC |
R4-2206184 |
(reserved) |
ETSI MCC |
R4-2206185 |
(reserved) |
ETSI MCC |
R4-2206186 |
(reserved) |
ETSI MCC |
R4-2206187 |
(reserved) |
ETSI MCC |
R4-2206188 |
(reserved) |
ETSI MCC |
R4-2206189 |
(reserved) |
ETSI MCC |
R4-2206190 |
(reserved) |
ETSI MCC |
R4-2206191 |
(reserved) |
ETSI MCC |
R4-2206192 |
(reserved) |
ETSI MCC |
R4-2206193 |
(reserved) |
ETSI MCC |
R4-2206194 |
(reserved) |
ETSI MCC |
R4-2206195 |
(reserved) |
ETSI MCC |
R4-2206196 |
(reserved) |
ETSI MCC |
R4-2206197 |
(reserved) |
ETSI MCC |
R4-2206198 |
(reserved) |
ETSI MCC |
R4-2206199 |
(reserved) |
ETSI MCC |
R4-2206200 |
(reserved) |
ETSI MCC |
R4-2206201 |
(reserved) |
ETSI MCC |
R4-2206202 |
(reserved) |
ETSI MCC |
R4-2206203 |
(reserved) |
ETSI MCC |
R4-2206204 |
(reserved) |
ETSI MCC |
R4-2206205 |
(reserved) |
ETSI MCC |
R4-2206206 |
(reserved) |
ETSI MCC |
R4-2206207 |
(reserved) |
ETSI MCC |
R4-2206208 |
(reserved) |
ETSI MCC |
R4-2206209 |
(reserved) |
ETSI MCC |
R4-2206210 |
(reserved) |
ETSI MCC |
R4-2206211 |
(reserved) |
ETSI MCC |
R4-2206212 |
(reserved) |
ETSI MCC |
R4-2206213 |
(reserved) |
ETSI MCC |
R4-2206214 |
(reserved) |
ETSI MCC |
R4-2206215 |
(reserved) |
ETSI MCC |
R4-2206216 |
(reserved) |
ETSI MCC |
R4-2206217 |
(reserved) |
ETSI MCC |
R4-2206218 |
(reserved) |
ETSI MCC |
R4-2206219 |
(reserved) |
ETSI MCC |
R4-2206220 |
(reserved) |
ETSI MCC |
R4-2206221 |
(reserved) |
ETSI MCC |
R4-2206222 |
(reserved) |
ETSI MCC |
R4-2206223 |
(reserved) |
ETSI MCC |
R4-2206224 |
(reserved) |
ETSI MCC |
R4-2206225 |
(reserved) |
ETSI MCC |
R4-2206226 |
(reserved) |
ETSI MCC |
R4-2206227 |
(reserved) |
ETSI MCC |
R4-2206228 |
(reserved) |
ETSI MCC |
R4-2206229 |
(reserved) |
ETSI MCC |
R4-2206230 |
(reserved) |
ETSI MCC |
R4-2206231 |
(reserved) |
ETSI MCC |
R4-2206232 |
(reserved) |
ETSI MCC |
R4-2206233 |
(reserved) |
ETSI MCC |
R4-2206234 |
(reserved) |
ETSI MCC |
R4-2206235 |
(reserved) |
ETSI MCC |
R4-2206236 |
(reserved) |
ETSI MCC |
R4-2206237 |
(reserved) |
ETSI MCC |
R4-2206238 |
(reserved) |
ETSI MCC |
R4-2206239 |
(reserved) |
ETSI MCC |
R4-2206240 |
(reserved) |
ETSI MCC |
R4-2206241 |
(reserved) |
ETSI MCC |
R4-2206242 |
(reserved) |
ETSI MCC |
R4-2206243 |
(reserved) |
ETSI MCC |
R4-2206268 |
TP for TR 37.717-41-11: DC_1A-7A-20A-38A_n78A |
ZTE Corporation |
R4-2206300 |
(reserved) |
Main Session |
R4-2206304 |
(reserved) |
Main Session |
R4-2206335 |
(reserved) |
Main Session |
R4-2206404 |
(reserved) |
Main Session |
R4-2206410 |
(reserved) |
Main Session |
R4-2206411 |
(reserved) |
Main Session |
R4-2206422 |
(reserved) |
Main Session |
R4-2206435 |
(reserved) |
Main Session |
R4-2206648 |
(reserved) |
Main Session |
R4-2206649 |
(reserved) |
Main Session |
R4-2206650 |
(reserved) |
Main Session |
R4-2206651 |
(reserved) |
Main Session |
R4-2206652 |
(reserved) |
Main Session |
R4-2206653 |
(reserved) |
Main Session |
R4-2206654 |
(reserved) |
Main Session |
R4-2206655 |
(reserved) |
Main Session |
R4-2206656 |
(reserved) |
Main Session |
R4-2206657 |
(reserved) |
Main Session |
R4-2206658 |
(reserved) |
Main Session |
R4-2206659 |
(reserved) |
Main Session |
R4-2206660 |
(reserved) |
Main Session |
R4-2206661 |
(reserved) |
Main Session |
R4-2206662 |
(reserved) |
Main Session |
R4-2206663 |
(reserved) |
Main Session |
R4-2206664 |
(reserved) |
Main Session |
R4-2206665 |
(reserved) |
Main Session |
R4-2206666 |
(reserved) |
Main Session |
R4-2206667 |
(reserved) |
Main Session |
R4-2206668 |
(reserved) |
Main Session |
R4-2206669 |
(reserved) |
Main Session |
R4-2206670 |
(reserved) |
Main Session |
R4-2206671 |
(reserved) |
Main Session |
R4-2206672 |
(reserved) |
Main Session |
R4-2206673 |
(reserved) |
Main Session |
R4-2206674 |
(reserved) |
Main Session |
R4-2206675 |
(reserved) |
Main Session |
R4-2206676 |
(reserved) |
Main Session |
R4-2206677 |
(reserved) |
Main Session |
R4-2206678 |
(reserved) |
Main Session |
R4-2206679 |
(reserved) |
Main Session |
R4-2206680 |
(reserved) |
Main Session |
R4-2206681 |
(reserved) |
Main Session |
R4-2206682 |
(reserved) |
Main Session |
R4-2206683 |
(reserved) |
Main Session |
R4-2206684 |
(reserved) |
Main Session |
R4-2206685 |
(reserved) |
Main Session |
R4-2206686 |
(reserved) |
Main Session |
R4-2206687 |
(reserved) |
Main Session |
R4-2206688 |
(reserved) |
Main Session |
R4-2206689 |
(reserved) |
Main Session |
R4-2206690 |
(reserved) |
Main Session |
R4-2206691 |
(reserved) |
Main Session |
R4-2206692 |
(reserved) |
Main Session |
R4-2206693 |
(reserved) |
Main Session |
R4-2206694 |
(reserved) |
Main Session |
R4-2206695 |
(reserved) |
Main Session |
R4-2206696 |
(reserved) |
Main Session |
R4-2206697 |
(reserved) |
Main Session |
R4-2206698 |
(reserved) |
Main Session |
R4-2206699 |
(reserved) |
Main Session |
R4-2206700 |
(reserved) |
Main Session |
R4-2206701 |
(reserved) |
Main Session |
R4-2206702 |
(reserved) |
Main Session |
R4-2206703 |
(reserved) |
Main Session |
R4-2206704 |
(reserved) |
Main Session |
R4-2206705 |
(reserved) |
Main Session |
R4-2206706 |
(reserved) |
Main Session |
R4-2206707 |
(reserved) |
Main Session |
R4-2206708 |
(reserved) |
Main Session |
R4-2206709 |
(reserved) |
Main Session |
R4-2206710 |
(reserved) |
Main Session |
R4-2206711 |
(reserved) |
Main Session |
R4-2206712 |
(reserved) |
Main Session |
R4-2206713 |
(reserved) |
Main Session |
R4-2206714 |
(reserved) |
Main Session |
R4-2206715 |
(reserved) |
Main Session |
R4-2206716 |
(reserved) |
Main Session |
R4-2206717 |
(reserved) |
Main Session |
R4-2206718 |
(reserved) |
Main Session |
R4-2206719 |
(reserved) |
Main Session |
R4-2206720 |
(reserved) |
Main Session |
R4-2206721 |
(reserved) |
Main Session |
R4-2206722 |
(reserved) |
Main Session |
R4-2206723 |
(reserved) |
Main Session |
R4-2206724 |
(reserved) |
Main Session |
R4-2206725 |
(reserved) |
Main Session |
R4-2206726 |
(reserved) |
Main Session |
R4-2206727 |
(reserved) |
Main Session |
R4-2206728 |
(reserved) |
Main Session |
R4-2206729 |
(reserved) |
Main Session |
R4-2206730 |
(reserved) |
Main Session |
R4-2206731 |
(reserved) |
Main Session |
R4-2206732 |
(reserved) |
Main Session |
R4-2206733 |
(reserved) |
Main Session |
R4-2206734 |
(reserved) |
Main Session |
R4-2206735 |
(reserved) |
Main Session |
R4-2206736 |
(reserved) |
Main Session |
R4-2206737 |
(reserved) |
Main Session |
R4-2206738 |
(reserved) |
Main Session |
R4-2206739 |
(reserved) |
Main Session |
R4-2206740 |
(reserved) |
Main Session |
R4-2206741 |
(reserved) |
Main Session |
R4-2206742 |
(reserved) |
Main Session |
R4-2206743 |
(reserved) |
Main Session |
R4-2207181 |
(reserved) |
BSRF Session |
R4-2207385 |
(reserved) |
BSRF Session |
R4-2207408 |
(reserved) |
BSRF Session |
R4-2207458 |
(reserved) |
BSRF Session |
R4-2207461 |
(reserved) |
BSRF Session |
R4-2207505 |
(reserved) |
BSRF Session |
R4-2207533 |
(reserved) |
BSRF Session |
R4-2207534 |
(reserved) |
BSRF Session |
R4-2207535 |
(reserved) |
BSRF Session |
R4-2207536 |
(reserved) |
BSRF Session |
R4-2207537 |
(reserved) |
BSRF Session |